http://qs321.pair.com?node_id=11120412


in reply to Looking for alternative for IPC::Shareable (or increase size)

There is no pre-set limit to the number of processes that can bind to data; nor is there a pre-set limit to the complexity of the underlying data of the tied variables[2]. The amount of data that can be shared within a single bound variable is limited by the system's maximum size for a shared memory segment (the exact value is system-dependent).

From IPC::Shareable. So it seems you hit an OS limit.

You think you want *unlimited* shared memory segments. That can't happen. Unless you specify a reasonable upper-bound and then try negotiating that with the OS. Or modify the logic of your program. Multiple shared segments to store a single string perhaps?

Replies are listed 'Best First'.
Re^2: Looking for alternative for IPC::Shareable (or increase size) -send in parts
by bliako (Monsignor) on Aug 07, 2020 at 09:00 UTC

    When your messages exceed the 64K limit why not communicate them in parts. Message 1 of 6, 2 of 6 etc. each 64K in size. The receiver through some metadata will know how to put them together.