| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: postgresql scalability issue |
| Date: | 2010-11-08 16:51:06 |
| Message-ID: | 4CD82A7A.3060006@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/08/10 7:33 AM, umut orhan wrote:
> Hi all,
>
> I've collected some interesting results during my experiments which I
> couldn't figure out the reason behind them and need your assistance.
>
> I'm running PostgreSQL 9.0 on a quad-core machine having two level
> on-chip cache hierarchy. PostgreSQL has a large and warmed-up buffer
> cache thus, no disk I/O is observed during experiments (i.e. for each
> query buffer cache hit rate is 100%). I'm pinning each query/process
> to an individual core. Queries are simple read-only queries (only
> selects). Nested loop (without materialize) is used for the join operator.
> ....
did pinning the processes to CPU cores make any measurable difference ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-08 17:09:39 | Re: Syntax of: alter table ... add constraint ... |
| Previous Message | Alban Hertroys | 2010-11-08 16:50:58 | Re: Syntax of: alter table ... add constraint ... |