pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gaetano Mendola <mendola@bigfoot.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Cc: Torsten Schulz <comic@be-a-part.de>
Subject: Re: Optimize
Date: Mon, 24 Nov 2003 21:56:17 +0100
Message-ID: <3FC27071.9000001@bigfoot.com> (raw)
In-Reply-To: <3FC27911.7070403@be-a-part.de>
References: <3FC26E96.9090101@be-a-part.de>
	<3FC267FB.806@bigfoot.com>
	<3FC27911.7070403@be-a-part.de>

Torsten Schulz wrote:

> Gaetano Mendola wrote:
> 
>> Torsten Schulz wrote:
>>
>>> Yes, I know: very difficult question, but I don't know what to do now.
>>>
>>> Our Server:
>>> Dual-CPU with 1.2 GHz
>>> 1.5 GB RAM
>>>
>>> Our Problem: We are a Community. Between 19 and 21 o clock we have 
>>> >350 User in the Community. But then, the Database are very slow. And 
>>> we have per CPU ~20-30% idle-time.
>>
>>
>>
>> May we know the postgres version that you are running and
>> see the query that run slow ?
> 
> 
> Postgres: 7.3.2
> Query: All queries
> 
> Configuration:
> max_connections = 1000  # Must be, if lower then 500 we become 
> connection-errors
> shared_buffers = 5000        # 2*max_connections, min 16
> max_fsm_relations = 1000    # min 10, fsm is free space map
> max_fsm_pages = 2000000      # min 1000, fsm is free space map
> max_locks_per_transaction = 64 # min 10
> wal_buffers = 2000            # min 4
> 
> sort_mem = 32768             # min 32
> vacuum_mem = 32768           # min 1024
> 
> fsync = false
> 
> enable_seqscan = true
> enable_indexscan = true
> enable_tidscan = true
> enable_sort = true
> enable_nestloop = true
> enable_mergejoin = true
> enable_hashjoin = true
> 
> effective_cache_size = 96000  # default in 8k pages

With 500 connection at the sime time 32MB for sort_mem can be too much.
What say "iostat 1"  and "vmstat 1" ?

Try also to reduce this costs:

random_page_cost = 2.5
cpu_tuple_cost = 0.005
cpu_index_tuple_cost = 0.0005


BTW take a query and show us the result of explain analyze.


Regards
Gaetano Mendola












view thread (8+ messages)  latest in thread

Message-ID: <3FC27071.9000001@bigfoot.com>
Permalink:  ../3FC27071.9000001@bigfoot.com/
Also on:    postgresql.org/message-id/3FC27071.9000001@bigfoot.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: mendola@bigfoot.com, comic@be-a-part.de
  Subject: Re: Optimize
  In-Reply-To: <3FC27071.9000001@bigfoot.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