This is my first foray into IPC::Shareable ... and I wanted to be sure that my script was using system-resources (shared-memory) in a reasonable way.
The %Sess hash could grow to have perhaps 100 entries .... and if each entries causes another 64Kbyte shared-memory segment to be created, that would probably be not a good idea.
I couldn't understand why semaphores were being created and why, even though the hash was quite small, so many 64Kbyte segments were being created.
It is now clear that I need to be a bit more sophisticated in what I store in the shared-memory segment ...
... especially if %Sess could have many many entries
For example, perhaps it might be better to convert the hash to a string (using Data::Dumper) and it is the string that is stored in the shared-memory segment.
Thank you for the explanation.
In reply to Re: IPC::Sharable ... curious ipcs -a results
by andyok
in thread IPC::Sharable ... curious ipcs -a results
by andyok
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |