On 04/26/2010 07:31 AM, Henning Westerholt wrote:
On Monday 26 April 2010, Alex Balashov wrote:
The htable size is static; it doesn't dynamically resize itself up to the next power of 2 after a certain utilisation threshold, right?
Hi Alex,
i think this is a static setting, as the memory is allocated on startup in shared memory. Do you've run into performance problems or memory size constraints with the htable module?
None whatsoever, I was just curious from a theoretical perspective.
The answer lets me know in an a priori way whether the htable is optimal for applications involving rapidly shrinking or contracting data sets, by several factors.