Hello all,
thanks a lot for your help so far. You all where right about the IDE drive is
somehow caching the data. See the test results below. I also get different
tps values every time I run pgbench on PC1 (between 300 and 80 tps for 100
transactions).
I don't think it's a good idea to disable
On Wed, Jul 12, 2006 at 10:16:40 -0600,
"Koth, Christian (DWBI)" <[EMAIL PROTECTED]> wrote:
>
> I have noticed a strange performance behaviour using a commit statement on
> two different machines. On one of the machines the commit is many times
> faster than on the other machine which has fast
On Wednesday 12 July 2006 09:16, Koth, Christian (DWBI) wrote:
> Hi,
>
> please help me with the following problem:
>
> I have noticed a strange performance behaviour using a commit statement on
> two different machines. On one of the machines the commit is many times
> faster than on the other mac
On Wed, 12 Jul 2006 10:16:40 -0600
"Koth, Christian (DWBI)" <[EMAIL PROTECTED]> wrote:
> I have noticed a strange performance behaviour using a commit statement on
> two different machines. On one of the machines the commit is many times
> faster than on the other machine which has faster hardwar
The IDE drive is almost certainly lying about flushing data to the disk.
Lower-end consumer drives often do.
What this means is that commits will be a whole lot faster, but the
database loses its ACID guarantees, because a power failure at the wrong
moment could corrupt the whole database.
If you
Hi,
please help me with the following problem:
I have noticed a strange performance behaviour using a commit statement on two
different machines. On one of the machines the commit is many times faster than
on the other machine which has faster hardware. Server and client are running
always on
