From: Joshua D. Drake <jd@commandprompt.com>
To: Joel Fradkin <jfradkin@wazagua.com>
Cc: 'Jim C. Nasby' <decibel@decibel.org>
Cc: 'Alvaro Herrera' <alvherre@dcc.uchile.cl>
Cc: 'Andreas Pflug' <pgadmin@pse-consulting.de>
Cc: 'Dave Page' <dpage@vale-housing.co.uk>
Cc: pgsql-performance@postgresql.org, ac@wazagua.com, wheyliger@wazagua.com, "'Steve Hatt'" <shatt@wazagua.com>
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
Date: Sat, 23 Apr 2005 08:35:52 -0700
Message-ID: <426A6B58.5070506@commandprompt.com> (raw)
In-Reply-To: <001701c5480e$57e7fad0$797ba8c0@jfradkin>
References: <001701c5480e$57e7fad0$797ba8c0@jfradkin>
Joel Fradkin wrote:
> I would very, very strongly encourage you to run multi-user tests before
> deciding on mysql. Mysql is nowhere near as capable when it comes to
> concurrent operations as PostgreSQL is. From what others have said, it
> doesn't take many concurrent operations for it to just fall over. I
> can't speak from experience because I avoid mysql like the plague,
> though. :)
>
> I am just testing the water so to speak, if it cant handle single user tests
> then multiple user tests are kind of a waste of time.
Joel I think you are missing the point on the above comment. The above
comment as I read is, o.k. you are having problems with PostgreSQL BUT
MySQL isn't going to help you and you will see that in multi-user tests.
MySQL is known to work very well on small databases without a lot of
concurrent sessions. I don't think anybody here would argue that.
Where MySQL runs into trouble is larger databases with lots of
concurrent connections.
> I am a little disappointed I have not understood enough to get my analyzer
> to use the proper plan, we had to set seqscan off to get the select from
> response_line to work fast and I had to turn off merge joins to get assoc
> list to work fast. Once I am up I can try to learn more about it, I am so
> glad there are so many folks here willing to take time to educate us newb's.
Sincerely,
Joshua D. Drake
Command Prompt, Inc.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jd@commandprompt.com, jfradkin@wazagua.com, decibel@decibel.org, alvherre@dcc.uchile.cl, pgadmin@pse-consulting.de, dpage@vale-housing.co.uk, shatt@wazagua.com
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
In-Reply-To: <426A6B58.5070506@commandprompt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox