Re: PHP web farms (i.e. why msession or something like it)
| From: | Yasuo Ohgaki | Date: | Thu, 30 May 2002 14:13:45 +0000 |
| Subject: | Re: PHP web farms (i.e. why msession or something like it) | ||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-84584@lists.php.net to get a copy of this message | ||
Marcus Börger wrote:
At 03:52 30.05.2002, Yasuo Ohgaki wrote:Well, it's difficult to know which one is faster until we actually implement it. As Mark point it out, MySQL has difficulty also. Both have pros. and cons. PostgreSQL support transaction and row level lock, while MySQL supports lock or page level rocks. (3.x) Besides, MySQL manual states that it does not perform well when insert and update is concurrently performed. A-I 1.4 (which is the case for session management) I'm interested in how well MySQL does the job, too. I may write session mysql, but it won't happen in near future. -- Yasuo Ohgaki <yohgaki@ohgaki.net> E-mail address has been changed.Steve Meyers wrote:From my expirience postgres is slower if you use referential integrity (what you should do) but this you cannot do in mysql (and therefore it is some kind of data storage but not a real rdbms).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.