You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, each string stored in the hashtable is allocated on the regular heap with its own malloc, which suffers from additional memory overhead (bookkeeping data + padding). This overhead can increase the heap size by 50-100 %.
Writing own heap for strings could make this a little bit more memory-efficient and maybe a little faster.
The text was updated successfully, but these errors were encountered:
Currently, each string stored in the hashtable is allocated on the regular heap with its own malloc, which suffers from additional memory overhead (bookkeeping data + padding). This overhead can increase the heap size by 50-100 %.
Writing own heap for strings could make this a little bit more memory-efficient and maybe a little faster.
The text was updated successfully, but these errors were encountered: