pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Magnus Hagander <mha@sollentuna.net>
Cc: Greg Stark <gsstark@mit.edu>
Cc: David Brown <time@bigpond.net.au>
Cc: Gregory Stark <pgsql-performance@postgresql.org>
Subject: Re: cpu_tuple_cost
Date: 16 Mar 2005 10:42:52 -0500
Message-ID: <874qfblhqb.fsf@stark.xeocode.com> (raw)
In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCE6C7095@algol.sollentuna.se>
References: <6BCB9D8A16AC4241919521715F4D8BCE6C7095@algol.sollentuna.se>

"Magnus Hagander" <mha@sollentuna.net> writes:

> What about the cache memory on the disk? Even IDE disks have some 8Mb
> cache today, which makes a lot of difference for fairly short scans.
> Even if it's just read cache. That'll bring the speed of random access
> down to a 1=1 relationship with sequential access, assuming all fits in
> the cache.

8MB cache is really insignificant compared to the hundreds or thousands of
megabytes the OS would be using to cache. You could just add the 8MB to your
effective_cache_size (except it's not really 100% effective since it would
contain some of the same blocks as the OS cache).

-- 
greg




view thread (20+ messages)  latest in thread

Message-ID: <874qfblhqb.fsf@stark.xeocode.com>
Permalink:  ../874qfblhqb.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/874qfblhqb.fsf@stark.xeocode.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: gsstark@mit.edu, mha@sollentuna.net, time@bigpond.net.au
  Subject: Re: cpu_tuple_cost
  In-Reply-To: <874qfblhqb.fsf@stark.xeocode.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