Re: Finding bottleneck

From: Tom Lane
Subject: Re: Finding bottleneck
Date: ,
Msg-id: 28801.1123515439@sss.pgh.pa.us
(view: Whole thread, Raw)
In response to: Re: Finding bottleneck  ("Merlin Moncure")
List: pgsql-performance

Tree view

Finding bottleneck  (Kari Lavikka, )
 Re: Finding bottleneck  (Gavin Sherry, )
 Re: Finding bottleneck  (Claus Guttesen, )
 Re: Finding bottleneck  ("Merlin Moncure", )
 Re: Finding bottleneck  ("Luke Lonergan", )
  Re: Finding bottleneck  (Kari Lavikka, )
   Re: Finding bottleneck  (Tom Lane, )
 Re: Finding bottleneck  ("Merlin Moncure", )
  Re: Finding bottleneck  (Tom Lane, )
  Re: Finding bottleneck  (Kari Lavikka, )
   Re: Finding bottleneck  (Tom Lane, )
    Re: Finding bottleneck  (Kari Lavikka, )
     Re: Finding bottleneck  (Tom Lane, )
    Re: Finding bottleneck  (Kari Lavikka, )
     Re: Finding bottleneck  (Tom Lane, )
 Re: Finding bottleneck  (Ron, )
 Re: Finding bottleneck  ("Merlin Moncure", )
  Re: Finding bottleneck  (Tom Lane, )
 Re: Finding bottleneck  ("Merlin Moncure", )
 Re: Finding bottleneck  ("Merlin Moncure", )
  Re: Finding bottleneck  (Tom Lane, )
 Re: Finding bottleneck  ("Merlin Moncure", )

"Merlin Moncure" <> writes:
>> Kari Lavikka <> 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


pgsql-performance by date:

From: Tom Lane
Date:
Subject: Re: Finding bottleneck
From: Tom Lane
Date:
Subject: Re: Why hash join instead of nested loop?