Thread: Postgres server getting slow!!
Hi
i am running a High availability Postgresql server on redhat
linux 9. I am using NFS mount of data directory from a shared storage. The server was running without problems for last two
months. The server is connected to a dialin router where all my company units dialin and update the database.
Concurrently i have some 25 to 50 connections at peak hours.
Following are the problems i am facing
1) When 3 or 4 clients connect to this server, the pids are created and
those pids are not killed even after the client disconnects.
after sometimes some 10 to 20 pids gets created and postgres reject client connections.
2) After one or two concurrent connections, the server slows down.
The postmaster occupies more than 90% of the memory.
3) Even when restarting server, after one or two connection from clients, the pids start increasing automatically to 10 or 13. This again slows down the server.
Please help me to sort out this issue
Thanks in advance .
Regards
N S
Thanks tom. I checked the client side software. The software closes connection when connected locally. But when connected through dialup,
this problem comes. I will check the ppp connection also.
Is there any method of killing old pids. And also any performance tuning to be done on postgresql.conf file.
The database now contains 20K records. Will that cause a problem?
Regds
Narayanan
On Sat, 29 Jan 2005 Tom Lane wrote :
>"Narayanan Subramaniam Iyer" <bunix@rediffmail.com> writes:
> > 1) When 3 or 4 clients connect to this server, the pids are created and
> > those pids are not killed even after the client disconnects.
>
>In that case your clients are not really disconnecting. Take a closer
>look at your client-side software.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
I checked to find out the cause of the problem, ppp is disconnecting properly and the user session is also closed smoothely.
But when a report query is run on the table containing 32500 records,
the memory shoots up from 50 MB to 500 MB(Total memory is 512 MB RAM).
After that the memory usage never comes down .When some 4 or 5 user
connects, the remaining memory is utilised in a very little way, and finally the 6th or 7th user is denied with database access.The server now becomes slow.
Will running vacuum help to solve the problem?
The total database dump is 50 MB and the /var/lib/pgsql/data contains
700 MB of data.
Which all paramters are required to be increased in postgresq.conf.
Regds
N S
On Sun, 30 Jan 2005 N S wrote :
>
>
>Thanks tom. I checked the client side software. The software closes connection when connected locally. But when connected through dialup,
>this problem comes. I will check the ppp connection also.
>Is there any method of killing old pids. And also any performance tuning to be done on postgresql.conf file.
>
>The database now contains 20K records. Will that cause a problem?
>
>Regds
>
>Narayanan
>
>On Sat, 29 Jan 2005 Tom Lane wrote :
> >"Narayanan Subramaniam Iyer" <bunix@rediffmail.com> writes:
> > > 1) When 3 or 4 clients connect to this server, the pids are created and
> > > those pids are not killed even after the client disconnects.
> >
> >In that case your clients are not really disconnecting. Take a closer
> >look at your client-side software.
> >
> > regards, tom lane
> >
> >---------------------------(end of broadcast)---------------------------
> >TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo@postgresql.org so that your
> > message can get through to the mailing list cleanly
Attachment
Thanks joshua
i tried running vacuum command,
vacuum database as well as vacuum <indvidual table names>
but even after that querying the database , the memory shoots up
as i mentioned in the previous mail and never comes down.
Also the old pids of connections established remains even after the
connection is closed.
Will backing up the complete database, dropping and recreating can
make any difference.
Kindly suggest
Thanks in advance
regards
N S
On Mon, 31 Jan 2005 Joshua D.Drake wrote :
>N S wrote:
>
>>I checked to find out the cause of the problem, ppp is disconnecting properly and the user session is also closed smoothely.
>>But when a report query is run on the table containing 32500 records,
>>the memory shoots up from 50 MB to 500 MB(Total memory is 512 MB RAM).
>>After that the memory usage never comes down .When some 4 or 5 user
>>connects, the remaining memory is utilised in a very little way, and finally the 6th or 7th user is denied with database access.The server now becomes slow.
>>
>>Will running vacuum help to solve the problem?
>>
>Sounds like you need to run vacuum and analyze. It also sounds like you
>may need to run vacuum full the first time.
>
>vacuum needs to be run regularly as does analyze.
>
>Sincerely,
>
>Joshua D. Drake
>
>
>>
>>The total database dump is 50 MB and the /var/lib/pgsql/data contains
>>700 MB of data.
>>
>>Which all paramters are required to be increased in postgresq.conf.
>>
>>
>>Regds
>>
>>N S
>>
>>On Sun, 30 Jan 2005 N S wrote :
>> >
>> >
>> >Thanks tom. I checked the client side software. The software closes connection when connected locally. But when connected through dialup,
>> >this problem comes. I will check the ppp connection also.
>> >Is there any method of killing old pids. And also any performance tuning to be done on postgresql.conf file.
>> >
>> >The database now contains 20K records. Will that cause a problem?
>> >
>> >Regds
>> >
>> >Narayanan
>> >
>> >On Sat, 29 Jan 2005 Tom Lane wrote :
>> > >"Narayanan Subramaniam Iyer" <bunix@rediffmail.com> writes:
>> > > > 1) When 3 or 4 clients connect to this server, the pids are created and
>> > > > those pids are not killed even after the client disconnects.
>> > >
>> > >In that case your clients are not really disconnecting. Take a closer
>> > >look at your client-side software.
>> > >
>> > > regards, tom lane
>> > >
>> > >---------------------------(end of broadcast)---------------------------
>> > >TIP 3: if posting/reading through Usenet, please send an appropriate
>> > > subscribe-nomail command to majordomo@postgresql.org so that your
>> > > message can get through to the mailing list cleanly
>>
>>
>>
>><http://clients.rediff.com/signature/track_sig.asp>
>
>
>
>-- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
>Postgresql support, programming shared hosting and dedicated hosting.
>+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
>PostgreSQL Replicator -- production quality replication for PostgreSQL
>
Thanks joshua
i tried running vacuum command,
vacuum database as well as vacuum <indvidual table names>
but even after that querying the database , the memory shoots up
as i mentioned in the previous mail and never comes down.
Also the old pids of connections established remains even after the
connection is closed.
Will backing up the complete database, dropping and recreating can
make any difference.
Kindly suggest
Thanks in advance
regards
N S
N S wrote:
> I checked to find out the cause of the problem, ppp is disconnecting
> properly and the user session is also closed smoothely.
> But when a report query is run on the table containing 32500 records,
> the memory shoots up from 50 MB to 500 MB(Total memory is 512 MB RAM).
> After that the memory usage never comes down .When some 4 or 5 user
> connects, the remaining memory is utilised in a very little way, and
> finally the 6th or 7th user is denied with database access.The server
> now becomes slow.
>
> Will running vacuum help to solve the problem?
>
Sounds like you need to run vacuum and analyze. It also sounds like you
may need to run vacuum full the first time.
vacuum needs to be run regularly as does analyze.
Sincerely,
Joshua D. Drake
>
> The total database dump is 50 MB and the /var/lib/pgsql/data contains
> 700 MB of data.
>
> Which all paramters are required to be increased in postgresq.conf.
>
>
> Regds
>
> N S
>
> On Sun, 30 Jan 2005 N S wrote :
> >
> >
> >Thanks tom. I checked the client side software. The software closes
> connection when connected locally. But when connected through dialup,
> >this problem comes. I will check the ppp connection also.
> >Is there any method of killing old pids. And also any performance
> tuning to be done on postgresql.conf file.
> >
> >The database now contains 20K records. Will that cause a problem?
> >
> >Regds
> >
> >Narayanan
> >
> >On Sat, 29 Jan 2005 Tom Lane wrote :
> > >"Narayanan Subramaniam Iyer" <bunix@rediffmail.com> writes:
> > > > 1) When 3 or 4 clients connect to this server, the pids are
> created and
> > > > those pids are not killed even after the client disconnects.
> > >
> > >In that case your clients are not really disconnecting. Take a closer
> > >look at your client-side software.
> > >
> > > regards, tom lane
> > >
> > >---------------------------(end of
> broadcast)---------------------------
> > >TIP 3: if posting/reading through Usenet, please send an appropriate
> > > subscribe-nomail command to majordomo@postgresql.org so that your
> > > message can get through to the mailing list cleanly
>
>
>
> <http://clients.rediff.com/signature/track_sig.asp>