Re: postgresql scalability issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: umut orhan <umut_angelfire(at)yahoo(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: postgresql scalability issue
Date: 2010-11-08 15:55:15
Message-ID: 25416.1289231715@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

umut orhan <umut_angelfire(at)yahoo(dot)com> writes:
> When I pin a single query to an individual core, its execution time is observed
> as 111 seconds. This result is my base case. Then, I fire two instances of the
> same query concurrently and pin them to two different cores separately. However,
> each execution time becomes 132 seconds in this case.

If the queries are fetching the exact same data, this seems unsurprising
--- you will have a lot of contention for page-level locks. A more
realistic case would involve concurrent queries looking at different
data. Perhaps overlapping sets of data, but not exactly the same data.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-11-08 15:55:22 Re: W3C Specs: Web SQL
Previous Message Andrew Dunstan 2010-11-08 15:49:52 Re: Should we use make -k on the buildfarm?