pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Qingqing Zhou <zhouqq@cs.toronto.edu>
To: pgsql-performance@postgresql.org
Subject: Re: insert performance for win32
Date: Thu, 3 Nov 2005 16:46:52 -0500
Message-ID: <dke0ft$i6$1@news.hub.org> (raw)
References: <6EE64EF3AB31D5448D0007DD34EEB3417DD79B@Herge.rcsinc.local>


""Merlin Moncure"" <merlin.moncure@rcsonline.com> wrote
>
> Running from remote, Time progression is:
> First  50k: 20 sec
> Second    : 29 sec
> [...]
> final:    : 66 sec
>
This may due to the maintainence cost of a big transaction, I am not sure 
... Tom?

> so, clear upward progression of time/rec.  Initial time is 2.5k
> inserts/sec which is decent but not great for such a narrow table.  CPU
> time on server starts around 50% and drops in exact proportion to insert
> performance.  My earlier gprof test also suggest there is no smoking gun
> sucking down all the cpu time.
>

Not to 100%, so this means the server is always starving. It is waiting on 
something -- of couse not lock. That's why I think there is some problem on 
network communication. Another suspect will be the write - I knwo NTFS 
system will issue an internal log when extending a file. To remove the 
second suspect, I will try to hack the source to do a "fake" write ...

Regards,
Qingqing 





view thread (53+ messages)  latest in thread

Message-ID: <dke0ft$i6$1@news.hub.org>
Permalink:  ../dke0ft$i6$1@news.hub.org/
Also on:    postgresql.org/message-id/dke0ft$i6$1@news.hub.org

 · 

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: zhouqq@cs.toronto.edu
  Subject: Re: insert performance for win32
  In-Reply-To: <dke0ft$i6$1@news.hub.org>

* 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