Skip site navigation (1) Skip section navigation (2)

Re: User concurrency thresholding: where do I look?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: User concurrency thresholding: where do I look?
Date: 2007-07-19 16:22:24
Message-ID: 200707190922.24497.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-performance
Alvaro,

> Have you messed with max_connections and/or max_locks_per_transaction
> while testing this?  The lock table is sized to max_locks_per_xact times
> max_connections, and shared memory hash tables get slower when they are
> full.  Of course, the saturation point would depend on the avg number of
> locks acquired per user, which would explain why you are seeing a lower
> number for some users and higher for others (simpler/more complex
> queries).

That's an interesting thought.  Let me check lock counts and see if this is 
possibly the case.

-- 
Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

pgsql-performance by date

Next:From: ArnauDate: 2007-07-19 16:44:48
Subject: Is it possible to know where is the "deadlock"
Previous:From: Alvaro HerreraDate: 2007-07-19 15:49:12
Subject: Re: User concurrency thresholding: where do I look?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group