-
Notifications
You must be signed in to change notification settings - Fork 79
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
Comments
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. |
yeah, I have that on my hard disc for 6 months already... As soon as I have some free time I will add this |
From hrld...@gmail.com 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
The text was updated successfully, but these errors were encountered: