From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: vacuumdb not letting me connect to db |
Date: | 2021-02-04 17:07:27 |
Message-ID: | efacaeb3-3c86-e7f2-a674-9087b812502f@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
What about disk IO? That's what really gets saturated when running 300 threads.
On 2/4/21 11:00 AM, Atul Kumar wrote:
> Hi,
>
> The CPU and RAM are normal even on 300 jobs ( only 1-4% of consumption)
> but I don’t understand one thing here that if max_connections is set to
> 700 then why I am not able to connect the db.
>
> As the running jobs (300) are lesser than half of max_connections.
>
>
> Regards
> Atul
>
>
> On Thursday, February 4, 2021, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at
> <mailto:laurenz(dot)albe(at)cybertec(dot)at>> wrote:
>
> On Thu, 2021-02-04 at 16:56 +0530, Atul Kumar wrote:
> > I have 160 GB of RAM, postgres 9.6 is running on the server.
> >
> > after upgrade I ran the below command:
> >
> > "/usr/edb/as9.6/bin/vacuumdb" -U 'enterprisedb' --verbose --all -j 300
> > --analyze-only
> >
> > after running that command I was not able to connect the database
> > using psql for few minutes.
>
> That is to be expected.
>
> If you have 300 processes performing I/O and using CPU, your machine
> will vertainly be overloaded.
>
> Yours,
> Laurenz Albe
> --
> Cybertec | https://www.cybertec-postgresql.com
> <https://www.cybertec-postgresql.com>
>
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Ravi Krishna | 2021-02-04 17:34:55 | Re: vacuumdb not letting me connect to db |
Previous Message | Ron | 2021-02-04 17:05:57 | Re: vacuumdb not letting me connect to db |