Skip site navigation (1) Skip section navigation (2)

Re: Memory Tuning

From: "Mitch Vincent" <mitch(at)venux(dot)net>
To: "Bruno Wolff III" <bruno(at)wolff(dot)to>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Memory Tuning
Date: 2001-03-30 15:18:56
Message-ID: 007c01c0b92c$bcf1b2b0$0b51000a@epox450 (view raw, whole thread or download thread mbox)
Lists: pgsql-general
If you could post the schema of your tables that you do the query against
and an EXPLAIN of the queries you're doing, perhaps we could further tune
your queries in addition to beefing up the memory usage of the backend..

Check this link out too.

Software development :
You can have it cheap, fast or working. Choose two.

----- Original Message -----
From: "Bruno Wolff III" <bruno(at)wolff(dot)to>
To: <pgsql-general(at)postgresql(dot)org>
Sent: Friday, March 30, 2001 9:45 AM
Subject: Memory Tuning

> I am looking for information on tuning memory usage for Postgres on Linux
> (2.2 kernel). In particular I have a lot of memory relative to the size
> of my database and am looking to reduce latency in queries.
> Searching goegle turned up a few other cases of people asking about memory
> tuning, but I didn't see any answers.
> I have tried increasing the memory allowed for in memory sorts and the
> estimate of available buffer caching. I haven't tried raising the buffer
> space per connection as the documenation didn't seem to indicate
> that that would help. This seems to have helped a little, but it is
> hard to tell since the current delay is about 1 second and the queries
> seem to happen faster when they are repeated after a short amount of
> time.
> For some idea of the specific problem, I am setting up a replacement
> web server for my hobby server. The new box has a 1GHz Tbird with 500MB
> of memory and a 20G 7200rpm IDE disk. The database is effectively static,
> with rows for 300 games, 4000 people and 11000 people/game ratings and
> a couple of other miscelaneous tables with a handful of rows each.
> I am mostly interested in reducing the latency of requests while
> the flexibility of using the database. Eventually there will be online
> entry so I don't want to switch to writing static files for the most of
> different possible reports.
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?

In response to


pgsql-general by date

Next:From: Bruce MomjianDate: 2001-03-30 15:52:52
Subject: Re: [SQL] Re: pg_dump potential bug -UNIQUE INDEX on PG_SHADOW Dont!! HELP
Previous:From: Geoff CaplanDate: 2001-03-30 15:17:21
Subject: Strange problems with phpPgAdmin

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group