"Select * " on 12-18M row table from remote machine thru JDBC - Performance nose-dives after 10M-ish records

From: antthelimey <antthelimey(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: "Select * " on 12-18M row table from remote machine thru JDBC - Performance nose-dives after 10M-ish records
Date: 2012-09-28 13:52:30
Message-ID: 1348840349990-5725853.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On machine 1 - a table that contains between 12 and 18 million rows
On machine 2 - a Java app that calls Select * on the table, and writes it
into a Lucene index

Originally had a fetchSize of 10,000 and would take around 38 minutes for 12
million, 50 minutes for 16ish million to read it all & write it all back out
as the lucene index

One day it started taking 4 hours. If something changed, we dont know what
it was

We tracked it down to, after 10 million or so rows, the Fetch to get the
next 10,000 rows from the DB goes from like 1 second to 30 seconds, and
stays there

After spending a week of two devs & DBA trying to solve this, we eventually
"solved" it by upping the FetchRowSize in the JDBC call to 50,000

It was performing well enough again for a few weeks

then...one day... it started taking 4 hours again

we tried upping the shared_buffer from 16GB to 20GB

And last night... it took 7 hours

we are using PGSQL 9.1

does anyone have ANY ideas?!

thanks much

--
View this message in context: http://postgresql.1045698.n5.nabble.com/Select-on-12-18M-row-table-from-remote-machine-thru-JDBC-Performance-nose-dives-after-10M-ish-records-tp5725853.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Deron 2012-09-28 15:10:26 Re: "Select * " on 12-18M row table from remote machine thru JDBC - Performance nose-dives after 10M-ish records
Previous Message John Nash 2012-09-28 10:58:42 Re: [PERFORM] Re: [PERFORM] exponentia​l performanc​e decrease, problem with version postgres + RHEL?