Folks,

just wanted to share some benchmark results from one long performance
study comparing MySQL, PostgreSQL and Oracle transactions throughput
and engine scalability on T2000 and V890 (under Solaris). Oracle
results are removed (of course , but other are quite interesting...
Findings are presented as it, following step by step learning and
tuning curve

So well, you may find:
- http://dimitrik.free.fr/db_STRESS.html - Benchmark kit description
- http://dimitrik.free.fr/db_STRESS_BMK_Part1.html -- first main part
- http://dimitrik.free.fr/db_STRESS_BMK_Part2_ZFS.html -- second
part including ZFS specific tuning

Tests were executed in Mar/Apr.2007 with latest v8.2.3 on that time.
Due limited spare time I was able to publish results only now...
Any comments are welcome!

Best regards!
-Dimitri

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

On 5/31/07, Dimitri <dimitrik.fr@gmail.com> wrote:
> just wanted to share some benchmark results from one long performance
> study comparing MySQL, PostgreSQL and Oracle transactions throughput
> and engine scalability on T2000 and V890 (under Solaris).

Interesting, if awfully cryptic. The lack of axis labels, the lack of
axis normalization, and the fact that you put the graphs for different
databases and parameters on separate pages makes it rather hard to
compare the various results.

Alexander.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Well, let's say I want to have compact graphs

So, few comments on graphs:
- Title: compact name of test and execution conditions
- X-axis: is always representing time scale
- Y-axis: is showing a value level (whatever)
- Legend: gives you a value Name and its metric (KB/s, Op/s, TPS, etc)

TPS: (transactions per second)
- ALL-tps TR_all: all transactions (READ+WRITE) per second level
- ALL-tps TR_Read: only READ tps level
- ALL-tps TR_Write: only WRITE tps level

I must say I was more intrested by databases tuning rather documenting
each my step... But well, without documenting there is no result
As well I did not think to compare database initially (don't know why
but it's always starting a small war between DB vendors ), but
results were so surprising so I just continued until it was possible
)

Rgds,
-Dimitri

On 5/31/07, Alexander Staubo <alex@purefiction.net> wrote:
> On 5/31/07, Dimitri <dimitrik.fr@gmail.com> wrote:
> > just wanted to share some benchmark results from one long performance
> > study comparing MySQL, PostgreSQL and Oracle transactions throughput
> > and engine scalability on T2000 and V890 (under Solaris).
>
> Interesting, if awfully cryptic. The lack of axis labels, the lack of
> axis normalization, and the fact that you put the graphs for different
> databases and parameters on separate pages makes it rather hard to
> compare the various results.
>
> Alexander.
>

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org