| From: | Andrea Suisani <sickpig(at)opinioni(dot)net> |
|---|---|
| To: | Craig James <cjames(at)emolecules(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Two identical systems, radically different performance |
| Date: | 2012-10-11 14:14:11 |
| Message-ID: | 5076D433.7090605@opinioni.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 10/09/2012 01:40 AM, Craig James wrote:
> Nobody has commented on the hyperthreading question yet ... does it really matter? The old (fast) server has hyperthreading disabled, and the new (slower) server has hyperthreads enabled.
>
> If hyperthreading is definitely NOT an issue, it will save me a trip to the co-lo facility.
sorry to come late to the party, but being in a similar condition
I've googled a bit and I've found a way to disable hyperthreading without
the need to reboot the system and entering the bios:
echo 0 >/sys/devices/system/node/node0/cpuX/online
where X belongs to 1..(#cores * 2) if hyperthreading is enabled
(cpu0 can't be switched off).
didn't try myself on live system, but I definitely will
as soon as I have a new machine to test.
Andrea
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2012-10-11 14:19:33 | Re: Two identical systems, radically different performance |
| Previous Message | Franck Routier | 2012-10-11 08:22:53 | Re: Drawbacks of create index where is not null ? |