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

Memory consumption #1

Open
glaslos opened this issue Sep 30, 2019 · 0 comments
Open

Memory consumption #1

glaslos opened this issue Sep 30, 2019 · 0 comments

Comments

@glaslos
Copy link

glaslos commented Sep 30, 2019

Hi, first of all, thanks for this library. It was very educational reading your implementation. I run into an issue when running the benchmarks. I quickly run out of memory. Seems like b.N get's very large on my system (i7, 16GB Mem) which exhausts the memory when setting up Unset and IsSet benchmarks or running Set benchmarks. I can limit the number of element and then do %numElements in the actual benchmark for Unset and IsSet bit might skew the bechmark and doesn't solve the issue for Set. Any suggestions on how to approach this issue? Maybe limit the size of the ipmap?

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

1 participant