pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: femski <hypertree@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres batch write very slow - what to do
Date: Tue, 13 Mar 2007 11:29:09 -0400
Message-ID: <2563.1173799749@sss.pgh.pa.us> (raw)
In-Reply-To: <9453712.post@talk.nabble.com>
References: <9452092.post@talk.nabble.com>
	<45F685B7.5040001@enterprisedb.com>
	<9453712.post@talk.nabble.com>

femski <hypertree@yahoo.com> writes:
> I am runing Postgres 8.2 on OpenSuse 10.2 with latest jdbc driver. I moved
> the app to be collocated with the server. Oracle takes 60 sec. Postgres 275
> sec. For 4.7 million rows.

> There are 4 CPUs on the server and one is runing close to 100% during
> inserts.
> Network history shows spikes of upto 60% of the bandwidth (Gnome System
> monitor graph).

It sounds like you're incurring a network round trip for each row, which
will be expensive even for a co-located application.  Perhaps Oracle's
JDBC driver is smart enough to avoid that.  I'm not sure what tricks are
available for bulk loading with our JDBC driver --- the page Heikki
mentioned explains things from a server perspective but I dunno how that
translates into JDBC.  The folks who hang out on pgsql-jdbc could
probably give you some tips.

			regards, tom lane



view thread (20+ messages)  latest in thread

Message-ID: <2563.1173799749@sss.pgh.pa.us>
Permalink:  ../2563.1173799749@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2563.1173799749@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, hypertree@yahoo.com
  Subject: Re: Postgres batch write very slow - what to do
  In-Reply-To: <2563.1173799749@sss.pgh.pa.us>

* 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