pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rob Nagler <nagler@bivio.biz>
Cc: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Wed, 22 Oct 2003 21:27:47 -0400
Message-ID: <25480.1066872467@sss.pgh.pa.us> (raw)
In-Reply-To: <16279.4988.496000.539525@gargle.gargle.HOWL>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
	<3F9006BF.40906@persistent.co.in>
	<16272.4154.489000.227676@gargle.gargle.HOWL>
	<200310170936.25997.josh@agliodbs.com>
	<16272.32044.80671.948532@jump.bivio.com>
	<x7d6cpcdsr.fsf@yertle.int.kciLink.com>
	<16279.4988.496000.539525@gargle.gargle.HOWL>

Rob Nagler <nagler@bivio.biz> writes:
> Here's the vmstat 5 at a random time:

>    procs                      memory    swap          io     system         cpu
>  r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us  sy  id
>  0  0  0 272372  38416  78220 375048   0   3     2     0    0     0   2   2   0
>  0  0  0 272372  30000  78320 375660   0   0    34   274  382   284   5   1  94
>  0  1  0 272372  23012  78372 375924   0   0    25   558  445   488   8   2  90
>  1  0  0 272368  22744  78472 376192   0   6   125   594  364   664   9   3  88

> And here's it during vacuum:

>    procs                      memory    swap          io     system         cpu
>  r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us  sy  id
>  1  2  1 277292   9620  72028 409664  46  32  4934  4812 1697   966   8   4  88
>  0  3  0 277272   9588  72096 412964  61   0  7303  2478 1391   976   3   3  94
>  2  2  0 277336   9644  72136 393264 1326  32  2827  2954 1693  1519   8   3  89

The increased I/O activity is certainly to be expected, but what I find
striking here is that you've got substantial swap activity in the second
trace.  What is causing that?  Not VACUUM I don't think.  It doesn't have
any huge memory demand.  But swapping out processes could account for
the perceived slowdown in interactive response.

			regards, tom lane



view thread (45+ messages)  latest in thread

Message-ID: <25480.1066872467@sss.pgh.pa.us>
Permalink:  ../25480.1066872467@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/25480.1066872467@sss.pgh.pa.us

 · 

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-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, nagler@bivio.biz
  Subject: Re: vacuum locking
  In-Reply-To: <25480.1066872467@sss.pgh.pa.us>

* 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