pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Vanns <james.vanns@framestore.com>
To: Martin French <Martin.French@romaxtech.com>
Cc: Jim Vanns <james.vanns@framestore.com>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-performance-owner@postgresql.org
Subject: Re: Odd blocking (or massively latent) issue - even with EXPLAIN
Date: Tue, 24 Jul 2012 10:34:11 +0100
Message-ID: <1343122451.12579.155.camel@sys367.ldn.framestore.com> (raw)
In-Reply-To: <OFD096C18F.C98A054A-ON80257A45.0032E783-80257A45.00332C2A@LocalDomain>
References: <1343032905.12579.3.camel@sys367.ldn.framestore.com>
	<OF4731D4BD.B722B5CE-ON80257A44.004B3A30-80257A44.004BABD3@LocalDomain>
	<1343054763.12579.110.camel@sys367.ldn.framestore.com>
	<OF7755750C.7073A920-ON80257A45.00249D8E-80257A45.00259C8D@LocalDomain>
	<1343119691.12579.151.camel@sys367.ldn.framestore.com>
	<OFD096C18F.C98A054A-ON80257A45.0032E783-80257A45.00332C2A@LocalDomain>

> > That latter test - won't that pretty much just read from the page
> cache?
> > 'sync' may well have forced dirty pages to disk but does it actually
> > evict them to?
> 
> Basically, the cache is avoided because of the size of the file.
> 6000000 blocks at 8k exceeds the size of RAM in the machine, so it
> *should* miss the cache and hit the disk directly. :)

Doh!

> > 
> > Anyway, that is off topic... perhaps ;)
> > 
> > Thanks again,
> > 
> > Jim
> > 
> 
> Cheers
> 
> Martin ============================================= Romax Technology
> Limited Rutherford House Nottingham Science & Technology Park
> Nottingham, NG7 2PZ England Telephone numbers: +44 (0)115 951 88 00
> (main) For other office locations see:
> http://www.romaxtech.com/Contact =================================
> =============== E-mail: info@romaxtech.com Website: www.romaxtech.com
> ================================= ================ Confidentiality
> Statement This transmission is for the addressee only and contains
> information that is confidential and privileged. Unless you are the
> named addressee, or authorised to receive it on behalf of the
> addressee you may not copy or use it, or disclose it to anyone else.
> If you have received this transmission in error please delete from
> your system and contact the sender. Thank you for your cooperation.
> =================================================
> 

-- 
Jim Vanns
Systems Programmer
Framestore




view thread (14+ messages)  latest in thread

Message-ID: <1343122451.12579.155.camel@sys367.ldn.framestore.com>
Permalink:  ../1343122451.12579.155.camel@sys367.ldn.framestore.com/
Also on:    postgresql.org/message-id/1343122451.12579.155.camel@sys367.ldn.framestore.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-performance@postgresql.org
  Cc: james.vanns@framestore.com, Martin.French@romaxtech.com, pgsql-performance-owner@postgresql.org
  Subject: Re: Odd blocking (or massively latent) issue - even with EXPLAIN
  In-Reply-To: <1343122451.12579.155.camel@sys367.ldn.framestore.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