| 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: 10
|
|
| Author |
|
|
littlepeaks
Veteran Cruncher USA Joined: Apr 28, 2007 Post Count: 748 Status: Offline Project Badges:
|
I recently gave in and upgraded one of my PCs to Windows 11. Now when I do MCM work units, it reports a very low CPU time. For instance, I recently completed MCM1_0196816_8019 and it reported Cpu time/ Elapsed time as 0.02 / 0.75 -- what's up with that? Also the results says I'm running Windows 10, when I'm running Windows 11.
----------------------------------------[Edit 1 times, last edit by littlepeaks at Feb 27, 2023 5:54:45 AM] |
||
|
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 638 Status: Offline Project Badges:
|
I presume the upgrade is to a more powerful machine so it makes sense that the CPU time is lower. Are the credits the same as on the old machine (or close).
----------------------------------------But then those times are small. What did you upgrade to? a Quantum computer? ![]() [Edit 1 times, last edit by BobbyB at Feb 27, 2023 3:17:16 PM] |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7844 Status: Offline Project Badges:
|
I recently gave in and upgraded one of my PCs to Windows 11. Now when I do MCM work units, it reports a very low CPU time. For instance, I recently completed MCM1_0196816_8019 and it reported Cpu time/ Elapsed time as 0.02 / 0.75 -- what's up with that? Also the results says I'm running Windows 10, when I'm running Windows 11. Would care to post a link to that work unit ? I would interesting to see what time the wingman had. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
littlepeaks
Veteran Cruncher USA Joined: Apr 28, 2007 Post Count: 748 Status: Offline Project Badges:
|
Results link is https://www.worldcommunitygrid.org/contribution/workunit/268536714
----------------------------------------And here is a result link from before the upgrade: https://www.worldcommunitygrid.org/contribution/workunit/261730620 Yes, it's a pretty speedy machine. The elapsed time is pretty normal for that machine for MCM work units, but historically, the CPU time on that machine is usually close to the elapsed time. And as an answer to BobbyB, this machine has been in service for over a year -- the only change is upgrading from Windows 10 to Windows 11. [Edit 3 times, last edit by littlepeaks at Feb 27, 2023 4:55:22 PM] |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7844 Status: Offline Project Badges:
|
That result is certainly a bit baffling. To have such a shift in magnitude simply by changing the OS begs for some explanation. Has Microsoft suddenly found some great new shortcut in the OS overhead ??? It would be illuminating to see if anyone else with similar machine specs has experienced such an incredible speedup or if anyone has seen this type of result.. Time will tell if it is only a one-off or if the results continue.
----------------------------------------If it does continue, that would be an incredible advance. We certainly won't know until they release more MCM units and you can see if the results are repeatable. More information is needed. Cheers
Sgt. Joe
----------------------------------------*Minnesota Crunchers* [Edit 1 times, last edit by Sgt.Joe at Feb 27, 2023 5:23:35 PM] |
||
|
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 2173 Status: Offline Project Badges:
|
And as an answer to BobbyB, this machine has been in service for over a year -- the only change is upgrading from Windows 10 to Windows 11. The BOINC client (rather than anything directly WCG related) is misidentifiying OS versions for years (and not that this would make a difference with crunching in the first place). I have machines that have been upgraded to Windows 10 four (4) years ago and it still shows up as Windows 8.1, a freshly installed Windows Server 2019 shows up as Windows Server 2016 and a couple other of such frivolities... ;-)Ralf |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges:
|
(Copied from the designated MCM1-task:)
[05:53:10] Initializing In reailty, that task ran some 44 minutes, nearly 45. Still quite fast. It would be illuminating to see if anyone else with similar machine specs has experienced such an incredible speedup or if anyone has seen this type of result.. A similar experience, not quite the same, was seen when this happened on my laptop: workunit 264654804 MCM1_0196470_5763_0 Linux Valid 2023-02-12T16:45:21 2023-02-16T11:05:23 4.75/4.77 99.1/53.8--------------------------------------------------------------------------------------------------------------------------------------- Details: MCM1_0196470_5763_1 Linux Ubuntu Valid 2023-02-12T16:45:45 2023-02-12T20:51:27 0.17/0.17 8.6/53.8 workunit 264645357 MCM1_0196464_1879_0 Linux Valid 2023-02-12T16:25:05 2023-02-13T16:18:36 7.25/7.26 93.2/50.9--------------------------------------------------------------------------------------------------------------------------------------- Details: MCM1_0196464_1879_1 Linux Ubuntu Valid 2023-02-12T16:25:13 2023-02-12T20:51:27 0.17/0.17 8.6/50.9 In these two cases, the CPU-times were about 8000 seconds, that's about 2.2 hours. Nevertheless, only 0.17 hours were recorded for both of them. Looking at the API, other tasks that were returned by me at that time also didn't have a proper CPU-time: CpuTime Elapsed Claimed Granted SentTime ReceivedTime WorkunitId Name It may have had something to do with the fact that the lid of the laptop was closed, which it normally isn't. Strange but true. |
||
|
|
littlepeaks
Veteran Cruncher USA Joined: Apr 28, 2007 Post Count: 748 Status: Offline Project Badges:
|
Yes, but on your machine, the CPU time and elapsed time are the same -- on mine, they're wayyyyyy different.
|
||
|
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 2173 Status: Offline Project Badges:
|
Yes, but on your machine, the CPU time and elapsed time are the same -- on mine, they're wayyyyyy different. Nothing unusual. I have a 10 core/20 thread i7 which is heaviliy used during the day time and there MCM1 WUs usually have something like 12h-15h "elapsed time" but only 1.5h-2h CPU time...Ralf MCM1_0196842_2645_1 Precision3660-1 Valid 2023-02-18 22:58:33 UTC 2023-02-24 22:58:33 UTC 2023-02-21 03:07:22 UTC 2.16 / 17.7 198.8 / 138.4 |
||
|
|
littlepeaks
Veteran Cruncher USA Joined: Apr 28, 2007 Post Count: 748 Status: Offline Project Badges:
|
I dunno. In your case the CPU time is 12.5% of the elapsed time.
In my case, .02 is only 2.67% of the elapsed time. And .02 is only 1.2 minutes. |
||
|
|
|