From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Meskes <meskes(at)postgresql(dot)org>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: mysql-pgsql comparison |
Date: | 2002-01-14 01:29:18 |
Message-ID: | Pine.LNX.4.30.0201132006040.2682-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane writes:
> > 1. Actually run the MySQL benchmark, to see what's wrong with it. (Note
> > that this is not the crashme test.)
>
> This would be a worthwhile thing to try, just to see if it exposes any
> PG weaknesses we didn't already know about. I have run crashme in the
> past (not recently though); but I've never found time for their
> benchmark.
Well, I attempted to run the benchmark today, and it's not dissimilar to
crashme in the sense that a) it tends to crash, and b) it's quite useless.
It's the same single-user "run select a whole bunch of times" sort of
thing that's not really interesting anymore. The MySQL 4.0 server was
consistently killed by the kernel during this test. The stable
3.something version didn't quite work either because of some "unknown
errors", so I only got some tests to run. But when was the last time
someone actually cared about the speed of alter table or drop index?
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Samuel | 2002-01-14 02:44:12 | Re: again, LIKE operator |
Previous Message | will trillich | 2002-01-13 23:46:23 | Re: using EXPLAIN in postgresql RULES? |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2002-01-14 01:35:34 | Release time |
Previous Message | Justin Clift | 2002-01-13 22:19:01 | Re: mysql-pgsql comparison |