Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 18
Posts: 18   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 2510 times and has 17 replies Next Thread
jpvanpe
Cruncher
France
Joined: Dec 13, 2006
Post Count: 24
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
32 core hyperthreaded not equal to 64 jobs ???

Hi,

I have a new 32 core hyperthreaded which will do nothing for the weekend.
I decided to put it to crunch and it runs "only" 32 jobs in //.
Task manager is showing 50% used sad
I was hoping to have 64 jobs for 60 hours.

Any reason for that? confused
[Sep 9, 2011 4:08:37 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: 32 core hyperthreaded not equal to 64 jobs ???

Hi,

Think the default in the profile is still 16 cores maximum. Suggest you clear the local preferences in the client [fat Clear button], hop over to the my grid > device manager > device profile and set the use to 100% CPU time and 32 64 processors and on next client - server connection you'd see it flip on the other 50%. (Hit project update in client to force the connection)

Let us know

--//--

edit: 64 of course ;)
----------------------------------------
[Edit 1 times, last edit by Former Member at Sep 9, 2011 8:18:58 PM]
[Sep 9, 2011 4:12:40 PM]   Link   Report threatening or abusive post: please login first  Go to top 
KWSN - A Shrubbery
Master Cruncher
Joined: Jan 8, 2006
Post Count: 1585
Status: Offline
Reply to this Post  Reply with Quote 
Re: 32 core hyperthreaded not equal to 64 jobs ???

There is also the "On multiprocessors, at most use: processors" option to check.
----------------------------------------

Distributed computing volunteer since September 27, 2000
[Sep 9, 2011 4:31:50 PM]   Link   Report threatening or abusive post: please login first  Go to top 
jpvanpe
Cruncher
France
Joined: Dec 13, 2006
Post Count: 24
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 32 core hyperthreaded not equal to 64 jobs ???

Thanks for your quick reply SekeRob.

I tried but unsuccessfully crying

32 jobs in // for 60 hours = 1920 hours, that's not too bad
[Sep 9, 2011 4:36:53 PM]   Link   Report threatening or abusive post: please login first  Go to top 
sk..
Master Cruncher
http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif
Joined: Mar 22, 2007
Post Count: 2324
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 32 core hyperthreaded not equal to 64 jobs ???

Device Manager, Device Profiles, Default (or whatever the computer uses),
On multiprocessors, at most use: 64 processors

I have mine set to use 4096 processors, just in case tongue
[Sep 9, 2011 4:42:05 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: 32 core hyperthreaded not equal to 64 jobs ???

Thanks for your quick reply SekeRob.

I tried but unsuccessfully crying

32 jobs in // for 60 hours = 1920 hours, that's not too bad

Specifically it's these field in the client associated profile (Default, Home, Work, School) to check:

Use no more than: 100 % of processor time

a little down...

On multiprocessors, at most use: 32 64 processors **
On multiprocessors, use: 100% of processors

And of course the clearing of local prefs to prevent conflict. Problem is the legacy setting ** does not show in the newer clients, but if set on an old client, wont go away, then the function being to go for the lowest of the 2.

--//--

edit: 64 of course ,)
----------------------------------------
[Edit 1 times, last edit by Former Member at Sep 9, 2011 8:19:43 PM]
[Sep 9, 2011 4:49:42 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Ingleside
Veteran Cruncher
Norway
Joined: Nov 19, 2005
Post Count: 974
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 32 core hyperthreaded not equal to 64 jobs ???

On multiprocessors, at most use: 32 processors **
On multiprocessors, use: 100% of processors

And of course the clearing of local prefs to prevent conflict. Problem is the legacy setting ** does not show in the newer clients, but if set on an old client, wont go away, then the function being to go for the lowest of the 2.

Hmm, quick test...
adds <max_cpus>1</max_cpus> to global_prefs_override.xml, and re-reads the file... and... nothing happened...

Nothing happens, since the BOINC client doesn't know, and doesn't care it doesn't know, anything about the deprecated #cpus that was last used in the v6.2.28-client. Well, the client just knows enough about this deprecated flag to not give any errors if you do include it, but it's not used.


As for not using all cores on 64-way systems, this problem has surfaced before, and if not mis-remembers the problem is still present in v6.12.3x and if so you'll need to use a work-around until v7 is released.

The work-around is to do this:
Add/edit cc_config.xml (located in your BOINC data-directory), and include minimum:
<cc_config>
<options>
<ncpus>64</ncpus>
</options>
</cc_config>

Save the file, and re-start BOINC-client.

Oh, and this is assuming you've got 64 cores (real or HT). Increase/decrease 64 as neccessary.
----------------------------------------


"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
[Sep 9, 2011 5:07:18 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: 32 core hyperthreaded not equal to 64 jobs ???

To quote from that WCG device profile:
If you are using version 6.2 of the software, then the number of processors used will be the lesser of the two fields below. If you are using a version before 6.2, then only the 'at most' field will be used.


Is it wrong?

Yes we know of the config override, but is that proper? It's too preposterous that 6.12.3x has not fixed this yet.

--//--
[Sep 9, 2011 5:15:02 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Bearcat
Master Cruncher
USA
Joined: Jan 6, 2007
Post Count: 2803
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 32 core hyperthreaded not equal to 64 jobs ???

Would you be kind and post your system specs? Am drooling just reading about one machine with 64 cores. Specifically, what processor are you using? Is this a work or personal machine? Am assuming its a 4P system using 8 core xeons.
----------------------------------------
Crunching for humanity since 2007!

----------------------------------------
[Edit 1 times, last edit by Bearcat at Sep 9, 2011 7:14:27 PM]
[Sep 9, 2011 7:11:51 PM]   Link   Report threatening or abusive post: please login first  Go to top 
sk..
Master Cruncher
http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif
Joined: Mar 22, 2007
Post Count: 2324
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 32 core hyperthreaded not equal to 64 jobs ???

On multiprocessors, at most use: 32 processors **
That would need to be 64 processors; 32core HT=64threads as Boinc sees a thread as a core.

Also interested in the spec; I expect its a quad socket E7 series system (8cores/16threads per socket). You could even have 80threads on the crazy high end CPUs, but you really are talking mortgage territory. Would be interesting to know the performance when running varying numbers of CEP2 tasks; in terms of the CPU time / Elapsed time delta.
[Sep 9, 2011 7:30:06 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 18   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread