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

Re: [PERFORM] MySQL vs PG TPC-H benchmarks

From: Grega Bremec <grega(dot)bremec(at)noviforum(dot)si>
To: Eduardo Almeida <edalmeida(at)yahoo(dot)com>
Cc: Jan Wieck <JanWieck(at)yahoo(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>,pgsql-advocacy(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] MySQL vs PG TPC-H benchmarks
Date: 2004-04-22 13:42:49
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-advocacypgsql-performance
...and on Thu, Apr 22, 2004 at 05:53:18AM -0700, Eduardo Almeida used the keyboard:
> - The configuration of the machine is:
> Dual opteron 64 bits model 240
> 960 GB on RAID 0
> Mandrake Linux 64 with Kernel 2.6.5  (I compiled a
> kernel for this test)
> Java SDK  java version "1.4.2_04"
> PostgreSQL JDBC pg74.1jdbc3.jar
> - The TPC-H configuration is:
> TPC-H 2.0.0
> 100GB
> load using flat files
> Refresh functions using java

I'll just add for the reference, to those that aren't aware of it, the Java
virtual machine for x86_64 only exists in the 1.5 branch so far, and it's so
utterly unstable that most every notable shuffling around in the memory
crashes it. :)

Hence the 1.4.2_04 is a 32-bit application running in 32-bit mode.

I won't be getting into how much this affects the benchmarks as I didn't
really get into how CPU- and memory-intensive the refresh functions are in
these, so as I said - let's keep it a reference.

    Grega Bremec
    Senior Administrator
    Noviforum Ltd., Software & Media

In response to


pgsql-performance by date

Next:From: Rod TaylorDate: 2004-04-22 13:46:48
Subject: Re: order by index, and inheritance
Previous:From: Eduardo AlmeidaDate: 2004-04-22 12:53:18
Subject: Re: [PERFORM] MySQL vs PG TPC-H benchmarks

pgsql-advocacy by date

Next:From: Eduardo AlmeidaDate: 2004-04-22 13:59:10
Subject: Re: [PERFORM] MySQL vs PG TPC-H benchmarks
Previous:From: Merlin MoncureDate: 2004-04-22 13:08:04
Subject: Re: Fwd: Re: [PERFORM] MySQL vs PG TPC-H benchmarks

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