| From: | Shaun Thomas <sthomas(at)peak6(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | <pgsql-performance(at)postgresql(dot)org>, Claire Chang <yenhsiac(at)yahoo(dot)com> |
| Subject: | Re: Postgres 8.4 memory related parameters |
| Date: | 2011-08-04 21:02:11 |
| Message-ID: | 4E3B08D3.606@peak6.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 08/04/2011 03:38 PM, Kevin Grittner wrote:
> You're probably going to get better performance by setting that to 2
> to 3 times the number of actual cores (don't county hyperthreading
> for this purpose), and using a connection pooler to funnel the 600
> user connections down to a smaller number of database connections.
Your note about Hyperthreading *used* to be true. I'm not sure exactly
what they did to the Intel nehalem cores, but hyperthreading actually
seems to be much better now. It's not a true multiplier, but our pgbench
scores were 40% to 60% higher with HT enabled up to at least 5x the
number of cores.
I was honestly shocked at those results, but they were consistent across
multiple machines from two separate vendors.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
sthomas(at)peak6(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer.php
for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2011-08-04 21:12:18 | Re: Postgres 8.4 memory related parameters |
| Previous Message | Kevin Grittner | 2011-08-04 20:38:35 | Re: Postgres 8.4 memory related parameters |