pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: 范国腾 <fanguoteng@highgo.com>
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Cc: 王亮 <wangliang@highgo.com>
Subject: how to debug the postgres performance issue
Date: Fri, 14 Sep 2018 09:34:20 +0000
Message-ID: <c48da347e2b048a5b4cff2f048c5330b@EX01.highgo.com> (raw)

Hi,

We are doing the performance test in two nodes system(active/standby). Now we find that the disk IO is very high but the CPU is low. Is there any method or tool to help us debug to find which function makes this issue?

We try to use the gprof but it does not help us. The result show the LWLockAssign(the shared buffer init) is called the most time. The other function is called no more that 33139. That seems no problem.

Could you please  give any suggestion how to debug the high IO/low CPU issue?

Thanks
Steven

===================================
no time accumulated

  %   cumulative   self              self     total
 time   seconds   seconds    calls  Ts/call  Ts/call  name
  0.00      0.00     0.00  9240928     0.00     0.00  LWLockAssign
  0.00      0.00     0.00    33139     0.00     0.00  ShmemAlloc
  0.00      0.00     0.00    33084     0.00     0.00  seg_alloc
….


view thread (3+ messages)  latest in thread

Message-ID: <c48da347e2b048a5b4cff2f048c5330b@EX01.highgo.com>
Permalink:  ../c48da347e2b048a5b4cff2f048c5330b@EX01.highgo.com/
Also on:    postgresql.org/message-id/c48da347e2b048a5b4cff2f048c5330b@EX01.highgo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: fanguoteng@highgo.com, pgsql-admin@lists.postgresql.org, wangliang@highgo.com
  Subject: Re: how to debug the postgres performance issue
  In-Reply-To: <c48da347e2b048a5b4cff2f048c5330b@EX01.highgo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox