Re: Physical sites handling large data

From: "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in>
To: pgsql-general(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us
Subject: Re: Physical sites handling large data
Date: 2002-09-17 06:37:24
Message-ID: 3D871AFC.3841.8559870@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 16 Sep 2002 at 17:01, Ericson Smith wrote:

> ... that sound you hear is the sound of me knocking my head against the
> brick wall in here...
>
> Well it looks like Tom Lane was right (as always) on this one. On our
> previous server, we had 4 Gigs of RAM and 1.6 Gigs of shared memory.
> Does this mean now that the OS is efficiently caching disk, and they our
> 320MB of shared memory is good enough?

Looks like you are asking but if you ask me you just proved that it's enough..

> Our database is about 4 Gigs at this point with some tables having
> hundreds of thousands or millions of records.
> Any definitive insight here as to why I'm running so well at this point?

I would suggest looking at pg metadata regarding memory usage as well as ipcs
stats. Besides what are the kernle disk buffer setting. I believe you are using
linux and these buffer settings can be controlled via/for bdflush.

Your typical ipcs usage would be a much valuable figure along with free..

And BTW, what's your vacuum frequency? Just to count that in..

Bye
Shridhar

--
Worst Vegetable of the Year: The brussels sprout. This is also the worst
vegetable of next year. -- Steve Rubenstein

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Davis 2002-09-17 06:56:06 Re: Open Source Database article
Previous Message Bruce Momjian 2002-09-17 06:11:41 Open Source Database article

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB SD 2002-09-17 07:33:34 Re: Proposal for resolving casting issues
Previous Message Tom Lane 2002-09-17 06:36:24 Re: Proposal for resolving casting issues