> Steve Meyers wrote: >> Well, you didn't try it with MySQL, which is significantly faster than >> Oracle and Postgres for most stuff. In any case, I agree that >> msession is probably a better solution -- I just think that having >> built-in MySQL session support would be a good thing for PHP. > > You can easily port session pgsql for mysql. > > BTW, as far as my benchmarks on session pgsql and files > handler, they are almost equal. I didn't benchmark > in detail, but I doubt mysql could be much faster than > PostgreSQL. Just my guess. MySQL's table locking during update pretty much make sure that performance will degrade under heavy load with many connections. PostgreSQL has a different problem. It doesn't lock the table except when you perform vacuum. Instead of locking, for updates, PostgreSQL simply adds a new row to the table. For every update a session value gets, a new physical "tuple" is added. If you have an active site, the table space grows to some number times the number of sessions times the size of your session data. In a database, each session update will incur (at a minimum) an fsync() call. > > -- > Yasuo Ohgaki > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
