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

benchmark missing space / mem used #16

Open
hiqsociety opened this issue Jul 11, 2021 · 3 comments
Open

benchmark missing space / mem used #16

hiqsociety opened this issue Jul 11, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@hiqsociety
Copy link

possible to include the benchmark of space / mem used?

@ticket-tagger ticket-tagger bot added the enhancement New feature or request label Jul 11, 2021
@rafaelkallis
Copy link
Owner

rafaelkallis commented Jul 24, 2021

hi @hiqsociety, would a make benchmark-mem command solve your needs? The command would run a file using valgrind massif. For the benchmark itself I would test two scenarios of interest: 1) uniformly distributed keys and 2) zipfian keys. I would fill the tree with nullptr values to only measure data structure overhead.

Would that solve your use case? Do you have any other parameter (dependent variable) wishes for the benchmark?

@superdolt
Copy link

yes, that'll be great.

by the way, is adaptive radix tree better than patricia trie? (compressed radix)

@rafaelkallis
Copy link
Owner

by the way, is adaptive radix tree better than patricia trie? (compressed radix)

I can't give you a clear answer, it depends, define your use-case/workload and run a benchmark.

You can think of ART as patricia + node compression. If you want to read I would suggest you go over the original paper https://db.in.tum.de/~leis/papers/ART.pdf

It also strongly depends on the implementation. Not every ART implementation will have the same performance.

Also "better" might not always mean "more performance". My implementation also tries to be developer friendly and sometimes this comes at a performance cost.

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

No branches or pull requests

3 participants