Hello all, I'm looking for some advice from people that have experience with inter-process messaging queues. If you have experience with this sort of thing, I would appreciate any advice you can give... I'm working on an application that is extremely performance-sensitive. And, we're passing a lot of messages back and forth between two running programs. We've been using Postgres for our messaging queues up to now, but our message volume seems a bit higher than what we'd expect Postgres to keep up with... many inserts/deletes from in/out queues seems to dirty a lot of memory and effect general database performance (we use the database significantly for other operations). One option we're looking at is local sockets. Another option is shared memory. Shared memory seems like it might not work as we need it, though, given the limited semaphore capabilities of PHP. Another option is msg_get_queue() operations. This will be a bigger deal... our client does not currently have --enable-sysvmsg built into their PHP, and they have 1800+ servers to update everytime something like this is changed. So, I'm leaning toward local sockets. I'm implementing this right now, so I can test the performance against the Postgres implementation. I will also implement and test other solutions if anyone can persuade me... ie. if you feel the msg_get_queue() stuff is worth the compile/installation effort. Any help will be appreciated. Thanks, Bob -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
