# bob@xxxxxxxxxxxxxxx / 2007-01-29 11:09:13 -0500: > 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). ... > 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. You'll be comparing a mammoth to a moth swarm. Do you actually need the persistence PostgreSQL gives you, or don't you mind if the other side is down? If you need to be sure that the receiver will process your message even if it's not up when you send the message, you'll end up reinventing a database. What version of PostgreSQL are you using? What's your vacuuming strategy? -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
