From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jeremy Haile" <jhaile(at)fastmail(dot)fm> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Insert performance slows down in large batch |
Date: | 2005-12-01 19:19:14 |
Message-ID: | 15960.1133464754@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"Jeremy Haile" <jhaile(at)fastmail(dot)fm> writes:
> 1) Why does the performance degrade as the table sizes grow? Shouldn't
> the insert performance remain fairly constant if there are no indexes or
> constraints?
Yeah, insert really should be a constant-time operation if there's no
add-on operations like index updates or FK checks. Can you get more
information about where the time is going with gprof or oprofile?
(I'm not sure if oprofile is available for RHEL4, but it is in Fedora 4
so maybe RHEL4 has it too.)
If you're not comfortable with performance measurement tools, perhaps
you could crank up a test case program that just generates dummy data
and inserts it in the same way as your real application does. If you
can confirm a slowdown in a test case that other people can look at,
we'd be happy to look into the reason for it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Riess | 2005-12-01 19:34:43 | Re: 15,000 tables |
Previous Message | Gavin M. Roy | 2005-12-01 19:08:59 | Re: 15,000 tables |