From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "James Mansion" <james(at)mansionfamily(dot)plus(dot)com>, "Scott Carey" <scott(at)richrelevance(dot)com> |
Cc: | "Flavio Henrique Araque Gurgel" <flavio(at)4linux(dot)com(dot)br>, "Fabrix" <fabrixio1(at)gmail(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Scalability in postgres |
Date: | 2009-06-05 14:42:45 |
Message-ID: | 4A28E8950200002500027601@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Scott Carey <scott(at)richrelevance(dot)com> wrote:
> If you wake up 10,000 threads, and they all can get significant work
> done before yielding no matter what order they run, the system will
> scale extremely well.
But with roughly twice the average response time you would get
throttling active requests to the minimum needed to keep all resources
busy. (Admittedly a hard point to find with precision.)
> I would think that the 4 or 5 most important locks or concurrency
> coordination points in Postgres have very specific, unique
> properties.
Given the wide variety of uses I'd be cautious about such assumptions.
> In particular, these are interesting references, (not only for
java):
With this wealth of opinion, perhaps they can soon approach IBM's JVM
in their ability to support a large number of threads. I'm rooting
for them.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-06-05 15:19:19 | Re: Scalability in postgres |
Previous Message | Kevin Grittner | 2009-06-05 14:29:11 | Re: Scalability in postgres |