Re: User concurrency thresholding: where do I look?

[Josh Berkus <josh(at)agliodbs(dot)com>]

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