Skip to content
This repository has been archived by the owner on Jul 7, 2020. It is now read-only.

Remove node cache from DataTree to improve performance #179

Closed
wants to merge 5 commits into from

Conversation

abramsm
Copy link
Contributor

@abramsm abramsm commented Aug 2, 2015

testing indicates that map jobs run faster without the cache. This version of code passes all unit tests but has not been through a complete hercules build. Hoping to merge this into master and then get the automated analysis from that.

abramsm and others added 5 commits July 23, 2015 15:37
…true. When true the ConcurrentTree's behavior is the same as before this commit. Nodes are cached up to the max cache size and then they are evicted to the backing page store. When the parameter is false the node cache is bypassed and puts/gets go directly to the IPageDB backing store.
@abramsm
Copy link
Contributor Author

abramsm commented Aug 3, 2015

closing this for now. @mspiegel pointed out a potential concurrency issue. all tests are passing but we believe an edge case failure is possible

@abramsm abramsm closed this Aug 3, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant