| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, "Kari Lavikka" <tuner(at)bdb(dot)fi> |
| Subject: | Re: Finding bottleneck |
| Date: | 2005-08-08 15:37:19 |
| Message-ID: | 28801.1123515439@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
>> Kari Lavikka <tuner(at)bdb(dot)fi> writes:
>>> samples % symbol name
>>> 13513390 16.0074 AtEOXact_CatCache
>>
>> That seems quite odd --- I'm not used to seeing that function at the top
>> of a profile. What is the workload being profiled, exactly?
> He is running a commit_delay of 80000. Could that be playing a role?
It wouldn't cause AtEOXact_CatCache to suddenly get expensive. (I have
little or no faith in the value of nonzero commit_delay, though.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kari Lavikka | 2005-08-08 16:19:09 | Re: Finding bottleneck |
| Previous Message | Merlin Moncure | 2005-08-08 15:24:42 | Re: Finding bottleneck |