VoIP Mailing List Archives

[jra at baylink.com]

On Sat, Apr 26, 2008 at 11:15:42AM +1000, Rob Hillis wrote:

[astmattf at gmail.com]

On 4/28/08, Jay R. Ashworth <jra at baylink.com> wrote:

[skoroneos at digital-o...]

[rob at hillis.dyndns.org]

Matt Florell wrote:

[mwatson at becon.org]

This is my understanding of hyper threading, which I believe to be accurate.

Basically, as some have mentioned previously, the OS 'sees' your single physical core processor as 2 logical processors, in generally, logical processors are treated exactly as if they were real processors, and in the case of many OS's. they probably don't understand the difference - Linux however does have specific SMT support for hyperthreaded cores.

Basically not all CPU instructions take the same amount of clock cycles to complete, some may take 3, some may take 7, etc.

Many of these clock cycles actually goto waste because the CPU is waiting for something, for example, an instruction that involves a fetch from memory, if this takes 7 clock cycles to complete, 4 of those cycles might go wasted while the CPU essentially just sits there and waits for the data to be fetched form RAM, L1 or L2, or L3 cache.

Hyperthreading essentially puts these wasted CPU cycles to use by allowing the CPU to execute a separate thread while it would otherwise be idle waiting.

To me Hyperthreading is an excellent technology... I;m all about efficiency and trying to maximize resource usage whenever possible... and that exactly what hyper threading does.

That all being said... Hyper threading should not be thought of as effectively doubling your CPU power... as previous posters have said, Hyper threading will result in single threaded applications actually running slower.. this is because you still have other background processes running which may run on the other logical processor which could steal CPU cycles away from your main application... since you essentially have 2 threads executing on the same physical core, there are going to be times when one thread has to wait extra clock cycles while the other thread is executing. Remember its only those normally "wasted" clock cycles that you are going to gain a performance boost out of by making use of them... only 1 thread can actually be executing at any given time, so the CPU has to schedule these and try balance the threads equally so they each get an equal share of the physical core.

I can't say how Asterisk behaves or makes use of additional cores or if hyper threading is advantageous to Asterisk or not... I don't know enough about the low level parts of Asterisk enough to make an informed opinion about that.

I just thought I'd throw in my 2 cents about what hyper threading is and what it does.

--
Matt
-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Rob Hillis
Sent: Tuesday, April 29, 2008 9:56 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Hyperthreading and multicore

Matt Florell wrote: