Re: [HACKERS] Priorities for 6.6

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Priorities for 6.6
Date: 1999-06-04 23:50:06
Message-ID: 199906042350.IAA01854@ext16.sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I obtained Oracle for Linux and did some comparisons with PostgreSQL
6.5 current using the test suite I mentioned before that is good to
create heavy loads.

With default postmaster settings (postmaster -S -i), PostgreSQL was
several times slower than Oracle. However with -F (postmaster -S -i -o
'-F'), PostgreSQL was much faster than the default settings. Yes, this
is well known behavior of PostgreSQL. Without -F PostgreSQL does
fsync() every time a transaction is committed, and it is the bottle
neck of the performance. I observed the disk activity LED almost
always on while running PostgreSQL without -F. However with -F, there
may be a chance that we loose committed data if the computer gets
crashed.

On the other hand the LED was on only every few secs while running
Oracle. I heard that Oracle has a "REDO log file" and a log is written
into there when a transaction is committed. If so, apparently Oracle
does not issue sync() or fsync() every time a transaction gets
committed. I don't know how Oracle guarantees the log be written into
the disk without sync() or fsync() at the commit time, but seems
something like it is one of the most important technique to enhance
the performance of PostgreSQL.

Does anybody have an idea on this?
---
Tatsuo Ishii

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 1999-06-05 00:18:07 Re: [HACKERS] Priorities for 6.6
Previous Message Oleg Bartunov 1999-06-04 23:20:59 problem with cvs ?