Re: [HACKERS] Some performance issues (since everybody is testing ... :) - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] Some performance issues (since everybody is testing ... :)
Date
Msg-id 34DB2EA2.9C8F0A1D@alumni.caltech.edu
Whole thread Raw
In response to Some performance issues (since everybody is testing ... :)  (Costin Oproiu <co@deuroconsult.ro>)
Responses Re: [HACKERS] Some performance issues (since everybody is testing ... :)  (Costin Oproiu <co@deuroconsult.ro>)
List pgsql-hackers
> I am starting with the conclusions to spare time:
>  - persistent connections invention stands somewhere between the fire and the
>    wheel
>  - unix sockets is not much compared to tcpip (at least on my Linux 2.0.30
>    box).
>  - parsing and executing a trivial "select 17;" accounts for a lot of time,
>    someone wanted hints on what is critical, profiler statistics coroborated.
>
>  Stressing postmaster with 100 connections

Hi. Since you are testing with multiple connections, would you like to try additional testing to make sure the new
deadlock
detection code behaves properly, especially under heavy load/multiple connections?

The large loading cases tend not to get exercised in beta testing because the systems are not in production yet...

                                              - Tom


pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Re: [QUESTIONS] is Postgres an SQL-based database?
Next
From: "Vadim B. Mikheev"
Date:
Subject: Re: [HACKERS] Profile of current backend