|
1)
Message boards :
Number crunching :
hours not being reported
(Message 12481)
Posted 27 days ago by entity Post: I just had one cancelled by server..... Replaced by version 4.37 |
|
2)
Message boards :
Number crunching :
Server down???
(Message 11934)
Posted 19 Dec 2025 by entity Post: But, it seems the forum is working. It is on the same domain name. Just the upload server? |
|
3)
Message boards :
Number crunching :
hours not being reported
(Message 11681)
Posted 20 Jul 2025 by entity Post: I wonder if this is the problem: traitement_v4 rise3 Not Running |
|
4)
Message boards :
Number crunching :
hours not being reported
(Message 11285)
Posted 8 Feb 2025 by entity Post: I've been running it for almost 12 hours and it isn't showing up on my account. Over the last 3 to 4 hours, NO HOURS are being logged to my account. ALL the runtime hours are the same totals they were around 20:00 UTC. |
|
5)
Message boards :
Number crunching :
hours not being reported
(Message 11282)
Posted 7 Feb 2025 by entity Post: WUProp not picking up hours from the BUDA application from the LLMentorGrid project. This is an application running in a docker container so WUProp probably doesn't recognize it. |
|
6)
Message boards :
Number crunching :
Server down???
(Message 11128)
Posted 19 Dec 2024 by entity Post: It's been my experience that this error won't fix itself. You have to reset the project and it will get another WU. |
|
7)
Message boards :
Number crunching :
hours not being reported
(Message 11126)
Posted 19 Dec 2024 by entity Post: No I haven't. I have been concentrating on 4_gaia for almost 10 days now. I'm just convinced that the WUProp app doesn't track runtime accurately for some reason. It misses minutes on some systems and hours on others. One just has to realize that if you are trying to get 100,000 hours on an application you will have to run close to 125,000 hours to achieve it. You just have to factor in the lost 25% in your planning. Since the website specifically states runtime and not CPU time, I'm expecting a 32 thread machine to have 32 hours of runtime per wall clock hour. If I get 30.5 to 31.5 then I accept that as accurate but that isn't what I'm getting. I even selected "Computers on this account" and added the daily activity for each computer and it doesn't match the hours displayed on the ACCOUNT page. Like I said, I have accepted the fact that this site isn't accurate and I am factoring that in my planning. |
|
8)
Message boards :
Number crunching :
hours not being reported
(Message 11124)
Posted 18 Dec 2024 by entity Post: All my systems seem to be counting hours fairly well (within 100 hours in a 24 hour period for systems with 32 threads or fewer). It's the 128 thread system that is missing about 1000 hours everyday. I'm wondering if there are other large systems that are missing hours too. If so, WUProp stats are not accurate. There is nothing indicating that anything is wrong on the system itself as all work units are executing in the time expected and are validating at the server end consistently. It's frustrating to know you are executing work you are not being given credit for. About 10 days or so ago I was consistently being credited with over 6000 hours everyday but then it stopped. |
|
9)
Message boards :
Number crunching :
hours not being reported
(Message 11121)
Posted 17 Dec 2024 by entity Post: This is potentially a big part of the problem: Tue 17 Dec 2024 09:06:59 AM CST | WUProp@Home | Scheduler request to https://wuprop.boinc-af.org/wuproj_cgi/cgi failed: Server returned nothing (no headers, no data) Has happened several times recently on different systems and other members have reported it too. The only way to fix is to reset the project. Almost 9 hours of compute time missing from a 128 thread server. |
|
10)
Message boards :
Number crunching :
hours not being reported
(Message 11117)
Posted 16 Dec 2024 by entity Post: Nothing I have any control over. Nothing out out of the ordinary happening on any of the machines running the code. All WUs start and end normally as expected (including wu_prop units). |
|
11)
Message boards :
Number crunching :
hours not being reported
(Message 11114)
Posted 16 Dec 2024 by entity Post: I have 280 threads running 4_Gaia and this has been consistent for at least a week now. 280 threads times 24 hours should be close to 6710 runtime hours per day but WU_Prop is only showing low 5000s. I would expect the hours to be within about 500 of 6710 depending on timing of WU reporting etc. I seem to be missing about 1500 hours everyday. I have always suspected the WU_Prop work units to miss some hours as they end, wait for upload, and then restart but not 1500 per day. |
©2026 Sébastien