Hyper Threaded P4

Message boards : Number crunching : Hyper Threaded P4
Message board moderation

To post messages, you must log in.

AuthorMessage
tickopa
Avatar

Send message
Joined: 8 Apr 02
Posts: 17
Credit: 62,691
RAC: 0
United Kingdom
Message 124615 - Posted: 17 Jun 2005, 17:08:17 UTC

The Task Manager shows a pair of setiathome_4.09 processes each at between about 45% to 49% of CPU time.
Boinc manager shows a pair of work units running at the same time but the progress numbers are different.
The question, is each work unit shared between the two processor threads or is each work unit allocated to one thread ?
ID: 124615 · Report as offensive
John McLeod VII
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 15 Jul 99
Posts: 24806
Credit: 790,712
RAC: 0
United States
Message 124619 - Posted: 17 Jun 2005, 17:12:59 UTC - in response to Message 124615.  

The Task Manager shows a pair of setiathome_4.09 processes each at between about 45% to 49% of CPU time.
Boinc manager shows a pair of work units running at the same time but the progress numbers are different.
The question, is each work unit shared between the two processor threads or is each work unit allocated to one thread ?

Processor affinity is not set. I believe that this means that the processes will normally stay with the CPU that they start on, but they could swap of both be on the same one for a bit if a higher priority task takes over one of the CPUs (virtual or real).


BOINC WIKI
ID: 124619 · Report as offensive
Pepo
Volunteer tester
Avatar

Send message
Joined: 5 Aug 99
Posts: 308
Credit: 418,019
RAC: 0
Slovakia
Message 124626 - Posted: 17 Jun 2005, 17:28:01 UTC - in response to Message 124619.  

The Task Manager shows a pair of setiathome_4.09 processes each at between about 45% to 49% of CPU time.
Boinc manager shows a pair of work units running at the same time but the progress numbers are different.
The question, is each work unit shared between the two processor threads or is each work unit allocated to one thread ?

Processor affinity is not set. I believe that this means that the processes will normally stay with the CPU that they start on, but they could swap of both be on the same one for a bit if a higher priority task takes over one of the CPUs (virtual or real).

A work unit is allocated to one thread. The thread could possibly move between the processors, until the affinity is set.
ID: 124626 · Report as offensive

Message boards : Number crunching : Hyper Threaded P4


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.