Re: concurrent connections is worse than serialization?

From: Richard Huxton <dev(at)archonet(dot)com>
To: Wei Weng <wweng(at)kencast(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: concurrent connections is worse than serialization?
Date: 2002-08-14 14:49:57
Message-ID: 200208141549.57646.dev@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Wednesday 14 Aug 2002 3:20 pm, Wei Weng wrote:
> On Wed, 2002-08-14 at 05:18, Richard Huxton wrote:
> > On Tuesday 13 Aug 2002 9:39 pm, Wei Weng wrote:

[30 connections is much slower than 1 connection 30 times]

> > What was the limiting factor during the test? Was the CPU maxed, memory,
> > disk I/O?
>
> No, none of the above was maxed. CPU usage that I paid attention to was
> at most a 48%.

Something must be the limiting factor. One of
- CPU
- Memory
- Disk I/O
- Database (configuration, or design)
- Application

If it's not CPU, is the system going into swap or are you seeing a lot of disk
activity?

> > I assume you've ruled the application end of things out.
>
> What does this mean?

I mean if you don't actually run the queries, then 30 separate processes is
fine?

If you can provide us with an EXPLAIN of the query and the relevant schema
definitions, we can rule out database design.

- Richard Huxton

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2002-08-14 15:20:09 Re: Explicite typecasting of functions
Previous Message philip johnson 2002-08-14 14:45:19 Re: pgsql-sql@postgresql.org