Re: Finding bottleneck

From: Merlin Moncure
Subject: Re: Finding bottleneck
Date: ,
Msg-id: 6EE64EF3AB31D5448D0007DD34EEB3417DD026@Herge.rcsinc.local
(view: Whole thread, Raw)
In response to: Finding bottleneck  (Kari Lavikka)
Responses: Re: Finding bottleneck  (Tom Lane)
Re: Finding bottleneck  (Kari Lavikka)
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", )

> 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?

Merlin


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?