From: | David Helgason <david(at)uti(dot)is> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | postgresql General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Large arrays give long lag on server side before command executes |
Date: | 2004-09-24 15:39:24 |
Message-ID: | E98572D7-0E3F-11D9-A5DE-000A9566DA8A@uti.is |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 24. sep 2004, at 16:32, Tom Lane wrote:
> David Helgason <david(at)uti(dot)is> writes:
>> Any suggestions how I go about finding the bottleneck here? What tools
>> do other people use for profiling on Linux.
>
> Rebuild with profiling enabled (make clean; make PROFILE="-pg
> -DLINUX_PROFILE")
> and then use gprof to produce a report from the trace file that the
> backend drops when it exits.
>
> If that sounds out of your league, send along a self-contained test
> case
> and I'll be glad to take a look.
I can try to make a self-contained test case, but right now there's a
10e6 dependancies, so it would be great if this is enough:
Attachment | Content-Type | Size |
---|---|---|
gprof data.zip | application/zip | 13.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-09-24 15:50:44 | Re: Large arrays give long lag on server side before command executes |
Previous Message | Oliver Nolden | 2004-09-24 15:37:19 | How to insert values in BYTEA? |