Re: Postgresql TPS Bottleneck

2022-04-20 Thread Benedict Holland
-- > *From:* Jeff Janes > *Sent:* Wednesday, April 20, 2022 5:49 PM > *To:* wakandavis...@outlook.com > *Cc:* Tomas Vondra ; > pgsql-performance@lists.postgresql.org < > pgsql-performance@lists.postgresql.org> > *Subject:* Re: Postgresql TPS Bottl

Re: Postgresql TPS Bottleneck

2022-04-20 Thread wakandavision
__ From: Jeff Janes Sent: Wednesday, April 20, 2022 5:49 PM To: wakandavis...@outlook.com Cc: Tomas Vondra ; pgsql-performance@lists.postgresql.org Subject: Re: Postgresql TPS Bottleneck On Wed, Apr 20, 2022 at 5:13 AM mailto:wakandavis...@outlook.com>> wrote: The next thing I did was

Re: Postgresql TPS Bottleneck

2022-04-20 Thread Jeff Janes
On Wed, Apr 20, 2022 at 5:13 AM wrote: > > The next thing I did was starting two independent Postgres instances on > the same server and run independent client applications against each of > them. This resulted in our application getting almost double of the TPS > compared to running a single ins

Re: Postgresql TPS Bottleneck

2022-04-20 Thread wakandavision
gresql.org Subject: Re: Postgresql TPS Bottleneck On 3/31/22 13:50, wakandavis...@outlook.com wrote: > Hi everyone, > > I am a bachelor's student and writing my thesis about the scaling and > performance of an application. The application is using postgresql as a > database

Re: Postgresql TPS Bottleneck

2022-03-31 Thread Mladen Gogala
On 3/31/22 07:50, wakandavis...@outlook.com wrote: Hi everyone, I am a bachelor's student and writing my thesis about the scaling and performance of an application. The application is using postgresql as a database but we can't scale any further currently as it seems postgres is hitting the limi

Re: Postgresql TPS Bottleneck

2022-03-31 Thread Tomas Vondra
On 3/31/22 13:50, wakandavis...@outlook.com wrote: > Hi everyone, > > I am a bachelor's student and writing my thesis about the scaling and > performance of an application. The application is using postgresql as a > database but we can't scale any further currently as it seems postgres > is hit

Re: Postgresql TPS Bottleneck

2022-03-31 Thread MichaelDBA
While setting these 2 parameters to off will make things go faster (especially for fsync), it is unrealistic to have these settings in a production environment, especiall fsync=off.  You might get by with synchronous_commit=off, but with fsync=off you could end up with corruption in your databa

Re: Postgresql TPS Bottleneck

2022-03-31 Thread Guillaume Cottenceau
writes: > Optimally I would like to fully use the CPU and get about 3-4 times > more TPS (if even possible). Disclaimer: I'm really not a pg performance expert. I don't understand your hope to fully use the CPU; if your scenario is disk-limited, which may very well be the case, then of course yo