> > 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.
No. We don't need the persistence. I'm planning on managing the flow and not sending the data if the app isn't available to receive it on the other end. > > What version of PostgreSQL are you using? 7.4.x > What's your vacuuming strategy? We've played around with a lot of them. Overall, it doesn't do too bad. But, we're trying to squeeze as much out of it as we can. > > -- > 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
