| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Smash Childhood Cancer
Thread: Why does SCC1 fall back to using the 32-bit binary for repair work for 64-bit wingmen? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges: 
|
 _0 is the infamous "Windows 8.1 x64" error: <core_client_version>7.2.47</core_client_version> <![CDATA[ <message> couldn't start app: CreateProcess() failed - A required privilege is not held by the client. (0x522) </message> ]]> I don't know why these people still insist on running 7.2.47 (from 2014, with obvious security vulnerabilities) when it's guaranteed to error out. I assume these are enterprise computers that have been abandoned due to job turnover. But I digress... My question is, the SCC1 application for the repair wingmen _1 and _2 are the 32-bit x86 versions -- which tend to have longer runtimes in my experience -- even though both _1 and _2 wingmen are running 64-bit OS's. Is this intended behavior or a bug? I experienced identical behavior when running HSTB and posted this thread: What determines whether client 7.26 or 7.16 is run & 32-bit vs. 64-bit? in January 2019 and updated in October 2019, but to this day there's been no replies. Can this please be fixed so that only the 64-bit binary is run for repair wingmen when they're both running 64-bit? I really dislike the inefficiency and longer runtimes when there's no reason [to my mind] to do so. If this is intended error behavior, can a WCG tech please explain the reasoning it fails to the x86 binary for both 64-bit wingmen? Thanks.
|
||
|
|
DrMason
Senior Cruncher Joined: Mar 16, 2007 Post Count: 153 Status: Offline Project Badges: 
|
Hey hchc. I'm actually not sure about this but have been curious. How can you tell from the results status screen whether an x86 or x64 version of the application was run? Or did you find out via your computer's task manager?
---------------------------------------- |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
Hey hchc. I'm actually not sure about this but have been curious. How can you tell from the results status screen whether an x86 or x64 version of the application was run? Or did you find out via your computer's task manager? Hey DrMason, I caught it in the act and used Task Manager in Windows. You're right that it's not visible in the Results Status. I posted that just to show that all 3 people are running 64-bit Windows.
[Edit 1 times, last edit by hchc at Apr 30, 2020 4:38:58 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just a guess: IF there is a purpose, this ensures the widest availability of repair clients in the pool of reliable hosts.
If you don't like it, there's a cc_config line to tell WCG to only send 64 bit apps, but since not all sciences are available in 64 bit compilation such as MIP1, you would not be able to participate in those. |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges:
|
since not all sciences are available in 64 bit compilation such as MIP1, I was wondering if this is also true for Linux.# ls -o ~boinc/projects/www.worldcommunitygrid.org/*_mip1_*-gnu |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
With the new 2023 SCC1 work units, I noticed this again.
----------------------------------------_0 Windows 10 64-bit _1 Windows 10 64-bit Yet both of us got the intelx86 (32-bit) work unit. It's totally weird how random it is.
|
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
Here's a fresh example of a Windows 11 64-bit device and a Windows 10 64-bit device both getting a SCC1 intelx86 (32-bit) work unit. It ran considerably slower than the 64-bit version of AutoDock Vina.
---------------------------------------- If I didn't any attention or answers from full-time IBM WCG sysadmins, I'm not holding my breath (as of April 2023) for Krembil/UHN WCG sysadmins to look into this, but I'd like to at least let them know this is still an issue for when they have the staffing and time to look into this.
|
||
|
|
|