From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | femski <hypertree(at)yahoo(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Postgres batch write very slow - what to do |
Date: | 2007-03-13 15:29:09 |
Message-ID: | 2563.1173799749@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
femski <hypertree(at)yahoo(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | vincent.moreau | 2007-03-13 15:46:34 | Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3 |
Previous Message | Joshua D. Drake | 2007-03-13 15:29:00 | Re: Autocommit in libpq |