Re^2: Convert script to use MySQL

There's no reason in my mind to continue to use MySQL except for legacy (software or people).

How about performance?

I'm working with a system that essentially does OLAP with a lot of updates. PostgreSQL (7.3.4) works great for it in theory, but in practice the system bogs down over a relatively short period of time (a few hours), and way down over the course of a day. We have to stop and vacuum the database nightly. A vaguely similar system I've worked on that uses MySQL (4.0.something with InnoDB tables) didn't suffer the same degradation.

Comment on Re^2: Convert script to use MySQL

Replies are listed 'Best First'.
Re^3: Convert script to use MySQL by Your Mother (Archbishop) on Nov 27, 2004 at 01:35 UTC
I've seen the same thing. I understand Postgres has addressed this issue in current versions but the version I was just doing contract work with (a year old I think) had memory leaks that meant it had to be restarted just about daily b/c the performance would spiral down to almost nothing. The MySQL I was working with 3 years ago had no trouble driving up to 10 million page views a day of data from a couple dozen different tables and I didn't admin it but I don't recall it needed restarting often if ever.	[reply]

Replies are listed 'Best First'.

Re^3: Convert script to use MySQL
by Your Mother (Archbishop) on Nov 27, 2004 at 01:35 UTC

I've seen the same thing. I understand Postgres has addressed this issue in current versions but the version I was just doing contract work with (a year old I think) had memory leaks that meant it had to be restarted just about daily b/c the performance would spiral down to almost nothing. The MySQL I was working with 3 years ago had no trouble driving up to 10 million page views a day of data from a couple dozen different tables and I didn't admin it but I don't recall it needed restarting often if ever.

[reply]