pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Brown <time@bigpond.net.au>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Planner really hates nested loops
Date: Fri, 04 Feb 2005 09:22:39 +1000
Message-ID: <4202B23F.5080604@bigpond.net.au> (raw)
In-Reply-To: <16694.1107447931@sss.pgh.pa.us>
References: <420206AD.8040206@bigpond.net.au>
	<16694.1107447931@sss.pgh.pa.us>

Tom Lane wrote:

>What exactly did you do to force the various plan choices?  (I see some
>ridiculous choices of indexscans, for instance, suggesting improper use
>of enable_seqscan in some cases.)
>
Except for forcing a hash with indexes (to show that increased use of 
indexes is not necessarily good), the "ridiculous choices of indexscans" 
are straight from the planner, i.e. I did not use enable_seqscan. 
Obviously, the alternative join methods were obtained by disabling hash 
joins and merge joins.

>  And what's the "cache rows" and "disk
>rows" stuff, and how do you know that what you were measuring is
>actually what you think it is?  I have zero confidence in
>Windows-atop-ATA as a platform for measuring disk-related behaviors,
>because I don't think you can control or even know what caching is
>going on.
>  
>
The terms are just abbreviated headings to make it easier to check what 
you're looking at. "Cache" refers to repeated runs without disk I/O. 
"Disk" refers to a completely initialized system with no PostgreSQL data 
in the OS cache (i.e. after a reboot - this is Benchmarking 101). All 
results were verified with *at least* two runs at different times. This 
is not to say the "disk" results are an accurate or absolute benchmark, 
but they're useful as a reference when looking at the cached results.

In any case, I can get the same "cached" results by increasing buffers 
to take up most of the memory and thereby make them the defacto cache.

With respect, could we please focus on the point of this thread? I've 
spent a great deal of time experimenting with PostgreSQL over the last 
couple of months, including reading every known web page regarding 
tuning and following every post in this list in that period. I'm 
confident that my results here are what most people will experience when 
trying PostgreSQL, and I'd like to help in a constructive way.



view thread (6+ messages)  latest in thread

Message-ID: <4202B23F.5080604@bigpond.net.au>
Permalink:  ../4202B23F.5080604@bigpond.net.au/
Also on:    postgresql.org/message-id/4202B23F.5080604@bigpond.net.au

 · 

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: time@bigpond.net.au, tgl@sss.pgh.pa.us
  Subject: Re: Planner really hates nested loops
  In-Reply-To: <4202B23F.5080604@bigpond.net.au>

* 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