On 12 Dec 2013, at 02:41, Ingo Walz wrote: > So socache with shared memory (shmcb) is the way you would suggest?
How important is the sharing in your case? If it's just about performance, you may be better-off accepting that each process will repeat the work of populating the hash, if that's a smaller overhead than IPC. If sharing is necessary, then socache will indeed serve, though you can leave the choice of socache engine to your config. I was also a little uneasy about your original description: the use of a forever-pool becomes a memory leak if it is populated with per-request data. Modules that do such things usually create their own pool (as a child of the process pool) which they can then maintain privately. -- Nick Kew
