Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve collection storage #107

Open
tzaeschke opened this issue Jun 24, 2017 · 0 comments
Open

Improve collection storage #107

tzaeschke opened this issue Jun 24, 2017 · 0 comments

Comments

@tzaeschke
Copy link
Owner

Currently, storage of collections, especially Map/Set, are not terribly efficient. One problem is that during deserilaization, the hashcode() function of all keys is called when they are added to a map/set.
This is partially done to avoid problems with schema compatibility between different Java versions.

Solution:

  • We could provide custom implementations. However these may have to be different for different Java versions, like Java 6, 7, 8...
  • We could try to use the Serialize/Externalize function, possibly by providing a 'Stream' that replaces references to FCOs withd OIDs. This may still cause problems if the serializableVersionUID changes.
  • We definitly should provide our own optimized implementations of SCO-HashMap/Set. We then could use these and replace Java-HashMap/Set on the fly, unless the user specifies otherwise.

The last options sounds like the best.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant