On Sep 25, 2006, at 10:58 AM, yoav x wrote:
I am not comparing Postgres to MyISAM (obviously it is not a very
fair comparison) and we do need
ACID, so all comparison are made against InnoDB (which now supports
MVCC as well). I will try
again with the suggestions posted here.
Make sure that
Hi
I am not comparing Postgres to MyISAM (obviously it is not a very fair
comparison) and we do need
ACID, so all comparison are made against InnoDB (which now supports MVCC as
well). I will try
again with the suggestions posted here.
Thanks.
--- Tom Lane [EMAIL PROTECTED] wrote:
yoav x
Hi
After upgrading DBI and DBD::Pg, this benchmark still picks MySQL as the winner
(at least on Linux
RH3 on a Dell 1875 server with 2 hyperthreaded 3.6GHz CPUs and 4GB RAM).
I've applied the following parameters to postgres.conf:
max_connections = 500
shared_buffers = 3000
work_mem = 10
On Thu, 2006-09-21 at 07:52 -0700, yoav x wrote:
Hi
After upgrading DBI and DBD::Pg, this benchmark still picks MySQL as the
winner (at least on Linux
RH3 on a Dell 1875 server with 2 hyperthreaded 3.6GHz CPUs and 4GB RAM).
I've applied the following parameters to postgres.conf:
Not to offend, but since most of us are PG users, we're not all that
familiar with what the different tests in MySQL's sql-bench benchmark
do. So you won't get very far by saying PG is slow on benchmark X, can
I make it faster?, because that doesn't include any of the information
we need in order
Hi.
Do you compare apples to apples? InnoDB tables to PostgreSQL? Are all
needed indexes available? Are you sure about that? What about fsync?
Does the benchmark insert a lot of rows? Have you tested placing the
WAL on a separate disk? Is PostgreSQL logging more stuff?
Another thing: have you
yoav x [EMAIL PROTECTED] writes:
I've applied the following parameters to postgres.conf:
max_connections = 500
shared_buffers = 3000
work_mem = 10
effective_cache_size = 30
Please see my earlier reply --- you ignored at least
checkpoint_segments, which is critical, and perhaps
On Thu, 2006-09-21 at 07:52 -0700, yoav x wrote:
Hi
After upgrading DBI and DBD::Pg, this benchmark still picks MySQL as the
winner (at least on Linux
RH3 on a Dell 1875 server with 2 hyperthreaded 3.6GHz CPUs and 4GB RAM).
I've applied the following parameters to postgres.conf:
On Thu, Sep 21, 2006 at 11:12:45AM -0400, Tom Lane wrote:
yoav x [EMAIL PROTECTED] writes:
I've applied the following parameters to postgres.conf:
max_connections = 500
shared_buffers = 3000
work_mem = 10
effective_cache_size = 30
You just told the database that you have
On 21-9-2006 23:49 Jim C. Nasby wrote:
Even with fsync = off, there's still a non-trivial amount of overhead
brought on by MVCC that's missing in myisam. If you don't care about
concurrency or ACIDity, but performance is critical (the case that the
MySQL benchmark favors), then PostgreSQL
10 matches
Mail list logo
