On Friday 01 February 2002 20:39, you wrote:
> That's the opposite of my experience, is all I can say. Under load MySQL
> becomes flaky as anything. It's thread management sucks, its query
> optimisation sucks, and when it goes down, it goes down hard.
That's again opposite of my experience. I've recently tried to setup a
20-30GB table in a database, which was a pain since the OS (Sun Cobalt's
Linux) didn't support files > 2GB and wasn't upgradeable. pg was totally
uncooperative at management (I never used it before, but all in all it took
longer than my first MySQL experience), and finally was out because of speed.
That box is as under-sized as can be, but I had no choice, so I did it in
MySQL with the latest table handlers. The result: It's definitely faster than
pg, it's faster at write access than MySQL's default table handler, it even
takes less space, and it's rock solid, even on this overloaded, small-memory,
small-processor, 50 vhosts, fscking Cobalt RaQ. (Thats about
1.000.000-1.500.000 rows in that one table)
I like it. And no, I never used triggers and suchlike before, I use MySQL
where it's best at: data repository, not application logic.
Btw, I'd like to hear more DB experiences, as it definitely touches our all
work one day or the other. How did you serialize XML to a db?
--
CU
Joerg
PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc
PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E 7779 CDDC 41A4 4C48 6F94
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
