Skip site navigation (1) Skip section navigation (2)

Firebird 1.5.3 X Postgresql 8.1.3 (linux and windows)

From: "andremachado" <andremachado(at)techforce(dot)com(dot)br>
To: pgsql-performance(at)postgresql(dot)org
Subject: Firebird 1.5.3 X Postgresql 8.1.3 (linux and windows)
Date: 2006-04-25 16:38:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
The performance comparison saga of the last month continues (see list archive).
After some time experimenting on windows, the conclusion is clear:

windows is likely crap for databases other than MS-SQL.

I guess that MS-SQL uses lot of undocumented api calls, may run in kernel
mode, ring 0 and a lot of dirty tricks to get some reasonable performance.

Then, I asked my coleague to send a new FB dump and a Pg dump to try at my
desktop machine.
This time, the database is somewhat bigger. Around 20 million records.

The timings are attached. Tried to follow the same query sequence on both files.
Both databases are much more faster on linux than on windows, and the desktop
machine is not dedicated and tuned. (no scsi, no raid, many services enabled,
ext3 fs, etc).
At many of the queries, postgresql is faster, sometimes way MUCH faster.
But Firebird have very good defaults out of the box and a few of the queries
are really a pain in Postgresql.
Please, see the abismal timing differences at the last 2 queries, for example.
They used 100% cpu, almost no disk activity, no twait cpu, for loooong time to
Maybe these queries bring into the light some instructions weaknesses, or bad
Do you have some suggestions?

Andre Felipe Machado
linux blog

Attachment: queries_timing_firebird.txt.tar.gz
Description: application/x-gzip (1.7 KB)
Attachment: queries_timing_postgresql.txt.tar.gz
Description: application/x-gzip (9.8 KB)


pgsql-performance by date

Next:From: David WheelerDate: 2006-04-25 16:44:55
Subject: PL/pgSQL Loop Vs. Batch Update
Previous:From: ArnauDate: 2006-04-25 16:33:33
Subject: Re: Query on postgresql 7.4.2 not using index

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group