I assume you are referring to the very low CPU time reported for your task in that quorum?? I've inserted some url tags around your link to make it easier for others to see what you want them to see.
If you follow the link and click on the Task ID of your task (ID=268142321), you will see that a full 9.5 hours was spent crunching that result and as you browse through the entire file, there doesn't seem to be anything amiss. Sometimes CPU time can get misreported if a task stops and is restarted but there doesn't seem to be any evidence of that. Just one of BOINC's little mysteries :-).
Hi Gary,
My low cpu time was part of my question, but my wingman showed 0 runtime also.
If boinc does that type of thing occasionally then so be it. What I thought odd was 2 different anomalies in the same wu. If that's OK don't bother even replying.
Thanks
Weird WU 114435712
)
Then don't :-).
Probably nothing bad :-).
I assume you are referring to the very low CPU time reported for your task in that quorum?? I've inserted some url tags around your link to make it easier for others to see what you want them to see.
If you follow the link and click on the Task ID of your task (ID=268142321), you will see that a full 9.5 hours was spent crunching that result and as you browse through the entire file, there doesn't seem to be anything amiss. Sometimes CPU time can get misreported if a task stops and is restarted but there doesn't seem to be any evidence of that. Just one of BOINC's little mysteries :-).
You're welcome!
Cheers,
Gary.
Hi Gary, My low cpu time
)
Hi Gary,
My low cpu time was part of my question, but my wingman showed 0 runtime also.
If boinc does that type of thing occasionally then so be it. What I thought odd was 2 different anomalies in the same wu. If that's OK don't bother even replying.
Thanks
Joe B
RE: Hi Gary, My low cpu
)
Your wingman is running Boinc 5.8.16, that version doesn't report runtime,
Claggy