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

TreePVector is slow #4

Open
blackdrag opened this issue Mar 20, 2014 · 2 comments
Open

TreePVector is slow #4

blackdrag opened this issue Mar 20, 2014 · 2 comments

Comments

@blackdrag
Copy link
Collaborator

From [email protected] on 2009-03-30T02:18:33Z

according to tests.Benchmarks, TreePVector is the only PCollection which consistently
underperforms compared to its corresponding Java API class, ArrayList.

2-3 finger trees might provide a faster implementation, but there might also be some simple
bottleneck in the current code.

Original issue: http://code.google.com/p/pcollections/issues/detail?id=4

@blackdrag blackdrag added this to the backlog milestone Mar 20, 2014
@Groostav
Copy link

Groostav commented Dec 2, 2015

According to this video i found somewhere on the internet,(and when has a man in a google wave t-shirt ever lead you wrong?) 2-3 finger trees are bad and the better datastructure is the Bitmapped Vector Trie with a large branching factor (32 in clojure) is the way to go.

I would really like to see this.

@blackdrag
Copy link
Collaborator Author

yeah, I have that on my hard disc for 6 months already... As soon as I have some free time I will add this

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

3 participants