pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
To: amrit@health2.moph.go.th
Cc: PGsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Low Performance for big hospital server ..
Date: Mon, 03 Jan 2005 11:08:32 +0100
Message-ID: <opsj0ugixpcq72hf@musicbox> (raw)
In-Reply-To: <1104740336.41d8fff03ff3a@webmail.moph.go.th>
References: <1104634472.41d762681b548@webmail.moph.go.th>
	<20050102140828.GA21826@pobox.com>
	<1104683293.41d8211d62221@webmail.moph.go.th>
	<41D8AD42.1010806@coretech.co.nz>
	<1104728050.41d8cff2b2b29@webmail.moph.go.th>
	<41D8E406.1090501@coretech.co.nz>
	<1104740336.41d8fff03ff3a@webmail.moph.go.th>



> Decrease the sort mem too much [8196] make the performance much slower  
> so I use
> sort_mem = 16384
> and leave effective cache to the same value , the result is quite better  
> but I
> should wait for tomorrow morning [official hour]  to see the end result.

	You could also profile your queries to see where those big sorts come  
from, and maybe add some indexes to try to replace sorts by  
index-scans-in-order, which use no temporary memory. Can you give an  
example of your queries which make use of big sorts like this ?



view thread (38+ messages)  latest in thread

Message-ID: <opsj0ugixpcq72hf@musicbox>
Permalink:  ../opsj0ugixpcq72hf@musicbox/
Also on:    postgresql.org/message-id/opsj0ugixpcq72hf@musicbox

 · 

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: lists@boutiquenumerique.com, amrit@health2.moph.go.th
  Subject: Re: Low Performance for big hospital server ..
  In-Reply-To: <opsj0ugixpcq72hf@musicbox>

* 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