From: CAJ CAJ <pguser@gmail.com>
To: Ralph Mason <ralph.mason@telogis.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance Woes
Date: Wed, 9 May 2007 17:26:07 -0700
Message-ID: <467669b30705091726j31fce52fp2f49649be675d811@mail.gmail.com> (raw)
In-Reply-To: <5132236932388612597@unknownmsgid>
References: <5132236932388612597@unknownmsgid>
> I have several databases. They are each about 35gb in size and have about
> 10.5K relations (count from pg_stat_all_tables) in them. Pg_class is
> about 26k rows and the data directory contains about 70k files. These are
> busy machines, they run about 50 xactions per second, ( aproxx insert /
> update / delete about 500 rows per second).
>
> We started getting errors about the number of open file descriptors
>
> : 2007-05-09 03:07:50.083 GMT 1146975740: LOG: 53000: out of file
> descriptors: Too many open files; release and retry
>
> 2007-05-09 03:07:50.083 GMT 1146975740: CONTEXT: SQL statement "insert
> ….. "
>
> PL/pgSQL function "trigfunc_whatever" line 50 at execute statement
>
> 2007-05-09 03:07:50.083 GMT 1146975740: LOCATION: BasicOpenFile, fd.c:471
>
> 2007-05-09 03:07:50.091 GMT 0: LOG: 00000: duration: 12.362 ms
>
> 2007-05-09 03:07:50.091 GMT 0: LOCATION: exec_simple_query, postgres.c
> :1090
>
>
>
> So we decreased the max_files_per_process to 800. This took care of the
> error **BUT** about quadrupled the IO wait that is happening on the
> machine. It went from a peek of about 50% to peeks of over 200% (4 processor
> machines, 4 gigs ram, raid). The load on the machine remained constant.
>
What version of Pg/OS? What is your hardware config?
I had seen these errors with earlier versions of Pg 7.4.x which was fixed in
later releases according to the changelogs
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: pguser@gmail.com, ralph.mason@telogis.com
Subject: Re: Performance Woes
In-Reply-To: <467669b30705091726j31fce52fp2f49649be675d811@mail.gmail.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