Why use shared memory instead of a pipe or a socket? In fact, since the server already uses a socket, you could completely avoid the Perl script.
From what I've read, it's much faster to communicate between processes using shared memory.
Re the php script: I should have explained that a little better.
Currently there is 50 requests per second from this php script and there is 4 servers doing this simultaneously at the moment. This will scale up to 10+ servers. So opening a connection for each one, due to the connection overhead, slows the whole process down to much. Hence why we are using a single persistent connection open between the two servers.
I'm not overly familiar with pipes beyond using for logging type stuff. Can they facilitate a request/return type system to an already running script?
In reply to Re^2: Constant communication between processes
by citycrew
in thread Constant communication between processes
by citycrew
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |