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

Maps: Allocate the buckets themselves using the allocator #585

Open
mihails-strasuns opened this issue Jul 27, 2018 · 1 comment
Open

Maps: Allocate the buckets themselves using the allocator #585

mihails-strasuns opened this issue Jul 27, 2018 · 1 comment

Comments

@mihails-strasuns
Copy link

@hatem-oraby-sociomantic :

@david-eckardt-sociomantic mentioned that the buckets themselves can be allocated using the used allocator instead of the GC (e.g when using malloc allocator, the buckets themselves would malloc allocated as well).

For something like the malloc allocator this would give a further performance boost as a map's buckets wouldn't be scanned by the GC (which would yield in faster GC cycles as the GC would have less items to scan).

This is a place holder for the issue so it wouldn't be forgotten.

@mihails-strasuns
Copy link
Author

Extra suggestion from @gavin-norman-sociomantic was to reduce bucket indices and lengths from size_t to uint. This would limit the number of buckets and items per bucket to 4 billion (32-bits), which I think should be fine for all conceivable future use.

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

No branches or pull requests

1 participant