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

Feature: Improve Update and Delete performance by introducing parallelism #6

Open
chrisreu opened this issue Aug 11, 2014 · 1 comment

Comments

@chrisreu
Copy link

We discussed this idea before, but never really implemented it. Deletes and Updates generally have to traverse the whole StringMap. If i'm not mistaken, deletes are even implemented using update. This makes both operations potentially expensive.

There is a way to potentially speed up the updates, at least for big StringMap's. If we split up the StringMap at it's top level, we can traverse the resulting branches in parallel. After the parallel updates the branches can be merged again. Splitting and merging should be considered cheap here.

@sebastian-philipp
Copy link
Owner

My last comment was wrong. Another Idea would be to build a Stringmap of to-be-deleted keys and then call difference with the original StringMap

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

No branches or pull requests

2 participants