pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Yu-Ju Hong <yuru.hong@gmail.com>
To: pgsql-performance@postgresql.org
Subject: dbt2 performance
Date: Thu, 25 Feb 2010 16:23:53 -0500
Message-ID: <516a4a601002251323udcc2b41tf5a09b968bef3a7c@mail.gmail.com> (raw)

Hi,

I have a couple of questions about dbt2 performance.

1. I tested dbt2+postgresql 8.4.2 on my server, but the NOTPM is around only
320~390 with 10 connections and 30 warehouses. Increasing the number of
connections did not improve the throughput? The NOPTM number does not seem
very high to me. Should I try more configurations to see if it can be
improved? Are there any numbers I can compare with (NOPTM and response
time)?

2. Moreover, the disk utilization was high and the "await" time from iostat
is around 500 ms. Could disk I/O limit the overall throughput? The server
has 2 SATA disks, one for system and postgresql and the other is dedicated
to logging (pg_xlog). As far as I understand, modern database systems should
be CPU-bound rather than I/O-bound, is it because I did not perform adequate
performance tuning?

3. From "vmstat", the cpus spent around 72% of time idle, 25% waiting for
I/O, and only 2~3% left doing real work. I was surprised that the cpu
utilization was so low. Is that normal or could it be due to
misconfiguration? In my opinion, even if disk I/O may have been stressed,
70% of idle time was still too high.


Below are some specs/configurations that I used. Any suggestion is welcome.
Thanks!

server spec:
4 cores (2*Dual-Core AMD Opteron, 800MHz), 12GB ram
2 SATA disks, one for system and postgresql and the other is dedicated to
logging (pg_xlog)

postgres configuration:
30 warehouses
256MB shared_buffer
768MB effective_cache_size
checkpoint_timeout 1hr (All my tests are within 10 minutes interval, so
checkpointing should not interfere the performance)
I turned off fsync to see whether the performance could be improved.

Yu-Ju

view thread (4+ messages)  latest in thread

Message-ID: <516a4a601002251323udcc2b41tf5a09b968bef3a7c@mail.gmail.com>
Permalink:  ../516a4a601002251323udcc2b41tf5a09b968bef3a7c@mail.gmail.com/
Also on:    postgresql.org/message-id/516a4a601002251323udcc2b41tf5a09b968bef3a7c@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: yuru.hong@gmail.com
  Subject: Re: dbt2 performance
  In-Reply-To: <516a4a601002251323udcc2b41tf5a09b968bef3a7c@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox