Re: PL_strtab/SHAREKEYS and copy-on-write leak

NODEFAULT_SHAREKEYS as a build option is undocumented, untested, and has probably suffered much bitrot over the years.

Note that if you disable the shared key hash, then every object will use its own storage for every hash key. For example if a process creates 1000 objects, each being a hash with the same fixed set of keys (but differing values of course), then that process will store 1000 copies of each key.

I doubt that you can safely and reliably shrink PL_strtab via XS.

Dave.

Comment on Re: PL_strtab/SHAREKEYS and copy-on-write leak

Replies are listed 'Best First'.
Re^2: PL_strtab/SHAREKEYS and copy-on-write leak by eserte (Deacon) on Aug 16, 2018 at 13:44 UTC
Note that if you disable the shared key hash, then every object will use its own storage for every hash key. For example if a process creates 1000 objects, each being a hash with the same fixed set of keys (but differing values of course), then that process will store 1000 copies of each key. But on the other hand, using shareable keys on data hashes where sharing is unlikely gives you overhead. If Devel::Size is correct then sharing a key adds 24 bytes. Maybe it would be nice if it was possible to decide per-hash whether to share keys or not. Or even nicer, if perl objects wouldn't be based on hashes, then key sharing wouldn't be necessary at all.	[reply]
Re^3: PL_strtab/SHAREKEYS and copy-on-write leak by dave_the_m (Monsignor) on Aug 16, 2018 at 18:22 UTC
The plan at some point is to introduce hash vtables. This will allow hashes to have varying implementations, which then opens up such possibilities. Dave.	[reply]
Re^2: PL_strtab/SHAREKEYS and copy-on-write leak by sezal (Novice) on Jul 30, 2018 at 08:19 UTC
Dave, Attempt to disable DEFAULT_SHAREKEYS was no more then just attempt to proof my assumptions regrading PL_strtab. I understand its not a good idea for production. I also not sure shrinking of PL_strtab (even it it's possible) will help. Perl may not release memory to OS, thus copy-on-write will occur. From what I see in sv.c and util.c Perl doesn't provide any API to dynamically enable/disable DEFAULT_SHAREKEYS for new hashes. :( Thank you.	[reply]


Your skill will accomplish what the force of many cannot
	PerlMonks