You don't mention what version of PostgreSQL you are using...each release
tends to have dramatic performance related improvements, so if you are
using an older then v6.4.2 version, chances are upgrading will show
improved performance for you...
In article <z9NA2.164$xs5.220@news.rdc1.az.home.com>,
Dirk Leas <dirkl@home.com> wrote:
>I put together a trivial servlet that does a small query against a
>PostgreSQL table. I run a single instance through a browser and it comes
>back quickly. Since I think I read the postmaster isn't multi-threaded, I
>wanted to see what a bunch of concurrent requests would to, so I started 5
>threads which each hit the servlet 100 times with a 1 second delay between
>passes. The wheels fall off in terms of performance. I haven't begun to
>dig into it yet, but does this mean PostgreSQL can't be used in the servlet
>space where it's reasonable to expect 100s of concurrent hits? I'm using RH
>Linux 5.2, ServletExec 2.0, and JDK 1.1.7a. If I alter my JDBC driver/url
>and go against Oracle or SQL Server, I see an order of magnitude difference
>in performance (they perform better).
>
>Anybody already been there and figured this out? I'm definitely planning on
>using connection pooling, but I wanted to ensure comparable performance at
>this level first.
>
>TIA,
>Dirk
>
>
--
Marc G. Fournier scrappy@hub.org
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
