| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 16
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'm testing a server with 48 cores (4 x 12 core) but the WCG BOINC manager (v6.2.28) and the latest BOINC version (6.10.43) only show the number of CPU's as 32 for the benchmarks.
----------------------------------------This means that only 32 tasks are running at once and the CPU's (collectively) are only running at ~70%. See screenshot. I've made sure the config files and WCG profiles are set to it can use 100% CPU and use a maximum of 60 CPU's (just to be sure!) Any ideas? Is this a client limitation? Thanks Tony [Edit 1 times, last edit by Former Member at Apr 22, 2010 12:50:47 PM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
BOINC can see as many as are enabled. The top machine in BOINC Global is 96 cores [that we can see].
----------------------------------------As to work provision. WCG limits that to For client version 6.2.28 visit the website device profile. There is a # of processors and a % processors. Set to 48 and 100%, then do a project update in the client. edit: oddly, 6.10.43 was supposed to ignore the # processors field, according a code expert who posts on these forums, so not sure wazzup with that. Just remembered that the work provision limit was upped to 32 x 80. Was a note that this was going to be moved as production setting beginning of March.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 2 times, last edit by Sekerob at Apr 20, 2010 11:10:47 AM] |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
Long ago I remember having read that there is no theoretical maximum in the BOINC client but that the distributed modules had a hardcoded maximum and that people needing more had to compile their own version.
----------------------------------------Could it be that? |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
I've made sure the config files and WCG profiles are set to it can use 100% CPU and use a maximum of 60 CPU's (just to be sure!) Any ideas? Is this a client limitation? Hmm, I don't know of any limitations, but when again I don't have a 48-core computer to test it on so wouldn't detect it anyway... But, just make sure, I would double-check you're using the correct "venue", it's configured to 100%, it's not being overriden by local preferences, and also make sure you've not got a cc_config.xml with <ncpus>32</ncpus> in it. Also make sure client has downloaded the new preferences. Also, use the 64-bit BOINC-client, just in case... It shouldn't matter when it comes to #cpu's, but trying v6.10.45 instead of *.43 would also be an idea... If nothing of this works, and it still only detects 32 cores, make yourself a cc_config.xml -file, and place it in the BOINC data-directory (if not already present). It should minimum include: <cc_config> <options> <ncpus>48</ncpus> </options> </cc_config> See if this helps... ![]() "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." [Edit 2 times, last edit by Ingleside at Apr 20, 2010 5:26:56 PM] |
||
|
|
Jason1478963
Senior Cruncher United States Joined: Sep 18, 2005 Post Count: 295 Status: Offline Project Badges:
|
I would like to see this work and see some results from a setup like this. I'm guessing a setup like this would save a guy some money on the electric bill and replace an entire pharm of machines.
----------------------------------------Hope it works well for you ![]() |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
an entire pharm of machines. At first that could look like a typo, but when computers are contributing to WCG for finding drugs this spelling is OK. No offense intended, Jason. Happy crunching. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Fixed it! Thanks everyone!
----------------------------------------It was in fact the <ncpus>48</ncpus> setting. My local file did not have this setting at all, I added it and restarted the client and now have 48 CPU's! Some stats (if you're interested) from BoincView Total FPU Speed - 75.33 GFIOps Total integer speed - 158.1 GIOps Credits/H - 486.37 2354 floating point MIPS per CPU 4941 integer MIPS per CPU Although I've hit the "reached daily quota of 32 results" message now :( [Edit 1 times, last edit by Former Member at Apr 22, 2010 12:12:45 PM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
This value according the official Wiki and the BFS manuals is intended as debug line only and has caused some trouble also because the meaning of the zero as value was changed. Also -1 should allow to use all CPU's, but if 48 does the job, excellent. The cc_config.xml does not exist by default when installing BOINC. See http://boincfaq.mundayweb.com/index.php?language=1&view=91
----------------------------------------Plz would you edit to OP post tile and insert [RESOLVED] Happy crunching.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Apr 22, 2010 12:15:16 PM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
PS, think the catch was/is in first having 6.2.28 that considers both the website device parms of % and #, then once it's in the global_prefs.xml with a value of for instance <max_cpus>32</max_cpus>, it's stuck in. When I look through the file I see
----------------------------------------global <max_cpus>4</max_cpus> work <max_cpus>4</max_cpus> school <max_cpus>4</max_cpus> home <max_cpus>16</max_cpus> just curious what it says in yours and also if it appears in the global_prefs_override.xml. With 6.10.43 it should not when local prefs are updated in the client, but then since the value exists, it may override? We'll keep this one in mind for when the next monster cruncher reports for duty with same issue. edit: Added a X-link to this discussion into the Start Here FAQ Index for when my memory goes http://bit.ly/cb7c4l :D
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Apr 23, 2010 12:31:24 PM] |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
just curious what it says in yours and also if it appears in the global_prefs_override.xml. With 6.10.43 it should not when local prefs are updated in the client, but then since the value exists, it may override? We'll keep this one in mind for when the next monster cruncher reports for duty with same issue. Interestingly enough they've still not removed the #cpu's from the normal BOINC-web-preferences, possibly to be compatible with old v5.8.xx-clients and v5.10.xx-clients for users that can't upgrade, so the various <max_cpus> is whatever is currently configured on web-page. But, a quick test reveals v6.10.47 doesn't use this preferense, even if you manually adds it to the override-file and re-reads the preferences it's not used. So, the problem is more likely to do with either the cpu's is too new so isn't correctly detected, windows doesn't report #cpu's correctly possibly due to being "wrong" version to support so many cores, or BOINC does detect the cpu's correctly but doesn't manage to count longer than to 32... In either case, remembering the work-around for the next user having this problem should be fairly easy. ![]() ![]() "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
|