| 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: 13
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Was looking at the system requirement page and how running tasks are shown in Windows 10 Task Manager and am a bit puzzled
----------------------------------------Research Project Memory Available Disk Space Operating Systems So I have one ARP1 running wcgrid_arp1_wrf_7.27_windows_x86_64 which seems to run as 64 bit but then I have wcgrid_hst1_gromacs_7.26_windows_x86_64 with the suffix (32 bit), and indeed running as 32 bit. And there's only ever wcgrid_fahb_bedam_7.30_windows_intelx86 also with (32 bit) shown in Task Manager, and the footnotes telling there is only 32 bit for Windows, but 64 bit for Linux and Mac. All I understand, but why is wcgrid_hst1_gromacs_7.26_windows_x86_64 running as 32 bit?. The footnotes say there is a 64 bit version for windows, which x86_64 indicates is being sent. [Edit 2 times, last edit by Former Member at Nov 22, 2019 3:53:01 PM] |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
I have a related thread in the HSTB forum: What determines whether client 7.26 or 7.16 is run & 32-bit vs. 64-bit?
----------------------------------------I get that occasionally too: either the 32-bit binary is run and/or version 7.16 will run instead of 7.26. I don't understand why.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Not related. You get 7.16 when the wingman was computed in 32 bit, so yours needs running too in 32 bit, regardless if it's a 64 bit system. In my case the 64 bit labelled app 7.26 is executing as 32 bit. Suggests something not right in compiling. Momentarily have 2 x86_64 executing as 32 bit (per the OS, Windows 10 1910 insider).
----------------------------------------There's a way to config BOINC to only fetch and execute 64 bit apps, which would be the test, but then mip1 and fahb which seem only to exist in 32 bit would not be downloaded. Got 2 zika running with wcgrid_zika_7.08_windows_x86_64, and are properly executing in 64 bit, no (32 bit) suffix added by Task Manager as identifier. [Edit 2 times, last edit by Former Member at Oct 31, 2019 12:10:06 PM] |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
Read my thread again. I brought up two issues. :)
----------------------------------------
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It's simply that there are 32 bit systems out there which need a wingman processing in 32 bit, which is the 7.16 version. There is no bit to bit compatibility in the output of 7.26 to 7.16, which is why. The distributor just sends a tasks to any system (32/64) that can process 32 bit if the wingman so requires, regardless of bit size of the receiving Client's OS.
----------------------------------------As for service v user app installation, mine is service. The bit level of the client does not impact the processing of the science... remember, BOINC is just a traffic manager. Something is not right how this particular x86_64 is identifying itself to the system. Potentially it could lead to results not matching if the wingman did process in 64 bit, but so far I've not seen invalids. It's just that processing in 64 bit is a nominal 4-8 percent faster, mst of the times. BOINC even got a method to determine if a 32 bit app of the science is faster, yes it can be, be never heard WCG employing this system which requires about 10-20 result comparisons run in the 2 bit sizes. Anyway, like to hear from techs, as to the root of this... app 64 bit, client 64 bit, OS 64 bit... processing 32 bit. [Edit 1 times, last edit by Former Member at Oct 31, 2019 12:28:13 PM] |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
Good luck. I've been waiting for an answer to the exact same question since 1/31/19.
----------------------------------------
|
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
@lavaflow
We are investigating why the 64 bit HSTB binary is actually 32 bit. It could have been a mistake when loaded months ago. Thanks for the catch. -Uplinger |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
@uplinger, in case it helps, I narrowed it down in my January thread, post 1 part 2:
----------------------------------------2) On my Windows 10 box where BOINC is installed to run as a service, the 64-bit HSTB application runs, while on my other Windows 10 box where BOINC is installed regularly and not as a service, the 64-bit HSTB application runs but as a 32-bit process. In Task Manager: wcgrid_hst1_gromacs_7.26_windows_x86_64 vs.wcgrid_hst1_gromacs_7.26_windows_x86_64 (32-bit) The exact same binary executes as 64-bit when BOINC is running as a service but executes as 32-bit when not running as a service but as a standard user. Edit: Apparently in @lavaflow's case, he's running BOINC as a service but the 64-bit binary is still running as a 32-bit process for some reason. Edit 2: I'm showing wcgrid_hst1_gromacs_7.26_windows_x86_64 as: SHA2-256: bcfc9422fd86ef4691ff8cc61b55d60e5e2533c34fb39290e411f203e921bf5e SHA2-512: 8c91fb1dd7d35b8e626243a66dbfe655d0d95c40ceea5945309c5942794ffb0ce466f327332ee86efb226812584c5e0529 76c4204b72984dfce0d7ef9af24e20
[Edit 3 times, last edit by hchc at Nov 4, 2019 10:51:46 PM] |
||
|
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges:
|
We are running a beta test with the fix for this.
Announcement: https://www.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=616792 Thanks, armstrdj |
||
|
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges:
|
This fix has been promoted to production for Help Stop TB and the new app version of 7.30 should start going out.
Thanks, armstrdj |
||
|
|
|