pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jignesh K. Shah <J.K.Shah@Sun.COM>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, Alvaro Herrera <alvherre@commandprompt.com>
Subject: Re: User concurrency thresholding: where do I look?
Date: Fri, 20 Jul 2007 14:23:51 -0400
Message-ID: <12002.1184955831@sss.pgh.pa.us> (raw)
In-Reply-To: <46A0FA31.2080208@sun.com>
References: <200707190828.59088.josh@agliodbs.com>
	<200707191819.13899.josh@agliodbs.com>
	<15685.1184895926@sss.pgh.pa.us>
	<200707192138.39679.josh@agliodbs.com>
	<46A0FA31.2080208@sun.com>

"Jignesh K. Shah" <J.K.Shah@Sun.COM> writes:
> There are no hard failures reported anywhere. Log min durations does 
> show that queries are now slowing down and taking longer.
> OS is not swapping and also eliminated IO  by putting the whole database 
> on /tmp

Hmm.  Do you see any evidence of a context swap storm (ie, a drastic
increase in the context swaps/second reading reported by vmstat)?

			regards, tom lane



view thread (58+ messages)  latest in thread

Message-ID: <12002.1184955831@sss.pgh.pa.us>
Permalink:  ../12002.1184955831@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12002.1184955831@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, J.K.Shah@Sun.COM, josh@agliodbs.com, alvherre@commandprompt.com
  Subject: Re: User concurrency thresholding: where do I look?
  In-Reply-To: <12002.1184955831@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