pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Domenico Sgarbossa <domenico@xtecnica.com>
To: Rosser Schwarz <rschwarz@totalcardinc.com>
To: pgsql-performance@postgresql.org
Subject: Re: [BULK] Problems with vacuum!
Date: Fri, 11 Jun 2004 16:53:22 +0200
Message-ID: <004c01c44fc3$d7cdeaf0$70c8007e@xtecnica.it> (raw)
References: <003c01c44fbd$c84a6af0$2500fa0a@CardServices.TCI.com>

Thanks for your advice!

As I immagine the system released dinamically the shared memory .... the
problem is that
when , after vacuum, users runs my application (ERP) and the system swap on
disk so the global performance
decrease very fast until the system is so slow that I need to reboot the
server.

It seems that the cached memory isn't released by the system... so the
system begin to swap to disk!
The swap problem is very important, it makes useless run vacuum 'cause after
vacuum the system
begin to swap.... so my application runs very slow!

Could you explain me better your final advice please?

> Watching this "cached" value over normal usage of your machine to get
> a running average is how you come up with your effective_cache_size
> configuration directive.

what does this mean pratically?

thanks!

Distinti Saluti

Sgarbossa Domenico
X Tecnica S.R.L.
www.xtecnica.com
Tel: 049/9409154 - 049/5970297
Fax: 049/9400288

----- Original Message -----
From: "Rosser Schwarz" <rschwarz@totalcardinc.com>
To: "'Domenico Sgarbossa'" <domenico@xtecnica.com>;
<pgsql-performance@postgresql.org>
Sent: Friday, June 11, 2004 4:09 PM
Subject: RE: [BULK] [PERFORM] Problems with vacuum!


> while you weren't looking, Domenico Sgarbossa wrote:
>
> Compare the "cached" values in each run of top.
>
> Before: 67828K cached
>
> After: 833896K cached
>
> The kernel is caching your tables for you.  That memory isn't actually
> being -used-, in the active, "a process has claimed this memory" sense.
> If a process comes along that needs more memory than free, the kernel
> will flush some of those cached pages (to swap?) to make room for
> whatever the memory requirements of the newcomer are.
>
> Watching this "cached" value over normal usage of your machine to get
> a running average is how you come up with your effective_cache_size
> configuration directive.
>
> /rls
>
> --
> Rosser Schwarz
> Total Card, Inc.
>
>
>






view thread (11+ messages)  latest in thread

Message-ID: <004c01c44fc3$d7cdeaf0$70c8007e@xtecnica.it>
Permalink:  ../004c01c44fc3$d7cdeaf0$70c8007e@xtecnica.it/
Also on:    postgresql.org/message-id/004c01c44fc3$d7cdeaf0$70c8007e@xtecnica.it

 · 

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: domenico@xtecnica.com, rschwarz@totalcardinc.com
  Subject: Re: [BULK] Problems with vacuum!
  In-Reply-To: <004c01c44fc3$d7cdeaf0$70c8007e@xtecnica.it>

* 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