Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go ยป
No member browsing this thread
Thread Status: Active
Total posts in this thread: 152
Posts: 152   Pages: 16   [ Previous Page | 7 8 9 10 11 12 13 14 15 16 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 32666 times and has 151 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: New Beta Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21

Not sure what your specific CPU related elapsed time of _3 has anything to do with the time-span to return _1, which was cut off in 1.09 CPU hours. The equation stems from the number of FPOPS a task has in the header (it's a factor of FPOPS, something like factor 5 or 10). For your device that will have been 3.70 to hit the mark.
...
'Maximum elapsed time exceeded', is a little bit misleading. A generic term for both measuring CPU and GPU task limits, but it really is in the case of CPU tasks, meant to mean the max FPOPS done in CPU time as exceeded.
VERY misleading! Especially when WCG's Results Status page uses CPU Time and Elapsed Time to mean quite different measurements.
[Nov 5, 2013 2:28:41 PM]   Link   Report threatening or abusive post: please login first  Go to top 
rbotterb
Senior Cruncher
United States
Joined: Jul 21, 2005
Post Count: 401
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21

I upped my CPU to 100% on my device driver, but still getting the restarts on the Beta WUs.

Win 7-SP 1, 64 bit, 6 GB Memory, HP I7 1.6 GHz
[Nov 5, 2013 2:42:38 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: New Beta Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21

Received 3 beta tasks, with one currently running.

11/5/2013 9:15:11 AM | World Community Grid | Restarting task BETA_BETA_9999984_0994a_2 using beta17 version 721 in slot 6
11/5/2013 9:18:16 AM | World Community Grid | Task BETA_BETA_9999984_0994a_2 exited with zero status but no 'finished' file
11/5/2013 9:18:16 AM | World Community Grid | If this happens repeatedly you may need to reset the project.
11/5/2013 9:18:16 AM | World Community Grid | Restarting task BETA_BETA_9999984_0994a_2 using beta17 version 721 in slot 6
11/5/2013 9:21:21 AM | World Community Grid | Task BETA_BETA_9999984_0994a_2 exited with zero status but no 'finished' file
11/5/2013 9:21:21 AM | World Community Grid | If this happens repeatedly you may need to reset the project.
11/5/2013 9:21:21 AM | World Community Grid | Restarting task BETA_BETA_9999984_0994a_2 using beta17 version 721 in slot 6

Same restart issue that occurred on previous beta tasks.
Win 7, 64bit, 12 GB, 7.0.64

These 'if this happens...' and 'exited with zero status...' have a Start Here FAQ discussing them. Generally the source is an overtaxed system [or something blocking... an overzealous security suite suspicious of whatever], but what IS causing the taxing? Viewed same, but only few times on my W7-64 Octo with 8GB during the v7.19 test and only the first 5 incurred this, together. Was meant to profile the disk IO with Process Explorer, but did not get round to doing this... no such error repeated here.
[Nov 5, 2013 2:45:06 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: New Beta Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21

Not sure what your specific CPU related elapsed time of _3 has anything to do with the time-span to return _1, which was cut off in 1.09 CPU hours. The equation stems from the number of FPOPS a task has in the header (it's a factor of FPOPS, something like factor 5 or 10). For your device that will have been 3.70 to hit the mark.
...
'Maximum elapsed time exceeded', is a little bit misleading. A generic term for both measuring CPU and GPU task limits, but it really is in the case of CPU tasks, meant to mean the max FPOPS done in CPU time as exceeded.
VERY misleading! Especially when WCG's Results Status page uses CPU Time and Elapsed Time to mean quite different measurements.
The 'problem' is, one system runs at 60% throttle and the next at 100%. Measuring wallclock would then lead to different cut-offs, so CPU tasks are CPU-time measured, GPU tasks are Elapsed time measured. I'm not a linguist [LoL], but making that message more generic with something like 'Maximum runtime exceeded' or 'Maximum FPOPS computed exceeded' would possibly avoid the confusion, albeit this is the first time I've seen this happening :D
[Nov 5, 2013 2:52:24 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Falconet
Master Cruncher
Portugal
Joined: Mar 9, 2009
Post Count: 3297
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21

<core_client_version>7.0.64</core_client_version>
<![CDATA[
<message>
aborted by user
</message>
<stderr_txt>
Commandline = projects/www.worldcommunitygrid.org/wcgrid_beta17_7.21_windows_x86_64 -SettingsFile BETA_9999979_0529.txt -DatabaseFile dataset-GDS2771-v1.txt
Initializing
wcg_learn_limit = 1000000
Running
[17:26:22]: Computing pass 0
INFO: WcgLearnLimit(1000000) reached. 0.7872723279251659 0.2886276180033747
INFO: WcgLearnLimit(1000000) reached. 1.3014459466739936 0.0041685254072945
INFO: WcgLearnLimit(1000000) reached. 0.4550874889953320 0.0040541684310824
INFO: WcgLearnLimit(1000000) reached. 1.3501830115455959 0.0106758112979151
INFO: WcgLearnLimit(1000000) reached. 1.0999860934953176 0.0059856545941557
INFO: WcgLearnLimit(1000000) reached. 1.2559925622012997 0.0012304127320135
INFO: WcgLearnLimit(1000000) reached. 0.4855671406448892 0.0010700417369094
INFO: WcgLearnLimit(1000000) reached. 1.5189882462323112 0.0168450912301523
INFO: WcgLearnLimit(1000000) reached. 0.9401926939665373 0.0070397653835244
INFO: WcgLearnLimit(1000000) reached. 1.2611300288499478 0.0024602310049886
INFO: WcgLearnLimit(1000000) reached. 0.3285909866863221 0.0892195942833496
INFO: WcgLearnLimit(1000000) reached. 1.3537617116844558 0.2851985241250077
Commandline = projects/www.worldcommunitygrid.org/wcgrid_beta17_7.21_windows_x86_64 -SettingsFile BETA_9999979_0529.txt -DatabaseFile dataset-GDS2771-v1.txt
Initializing
wcg_learn_limit = 1000000
Running

</stderr_txt>
]]>


After suspending it, it just hanged there barely recording any CPU time despite using a full core. I ended up aborting it.
It ran for more time than it is reported in the results status(1.46 wall clock reported vs around 2 hours and 30 minutes I saw on BOINC)
----------------------------------------


- AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W
- AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W
- AMD Ryzen 7 7730U 8C/16T 3.0 GHz
[Nov 5, 2013 3:03:13 PM]   Link   Report threatening or abusive post: please login first  Go to top 
KWSN - A Shrubbery
Master Cruncher
Joined: Jan 8, 2006
Post Count: 1585
Status: Offline
Reply to this Post  Reply with Quote 
Re: New Beta Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21

Now that it's (way too early) morning, here's the update on the stuck Windows tasks. They all finished so the results are there for the techs to look into.

None of my tasks restarted unless I stopped the service and restarted. They never lost CPU time, just completed %. Browsing over the returned results, they were approaching 12 hours CPU time. I know one of them in particular would repeatedly get to 75
% and just sit there for hours with both clocks incrementing.

Yes, this is not the last beta.
----------------------------------------

Distributed computing volunteer since September 27, 2000
[Nov 5, 2013 3:05:53 PM]   Link   Report threatening or abusive post: please login first  Go to top 
KWSN - A Shrubbery
Master Cruncher
Joined: Jan 8, 2006
Post Count: 1585
Status: Offline
Reply to this Post  Reply with Quote 
Re: New Beta Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21

And for another Windows system that I cannot monitor directly I see this:

BETA_ BETA_ 9999988_ 0993a_ 0-- L1-PC Pending Validation 11/4/13 20:28:00 11/5/13 12:54:54 1.44 / 8.42 122.7 / 0.0

Losing 70% + of time spent is a steep cost.
----------------------------------------

Distributed computing volunteer since September 27, 2000
[Nov 5, 2013 3:17:19 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: New Beta Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21

Received about 20 tasks
sofar not a single wu got past the 7 second CPU time
then after 90-120 seconds it restarts.
(infinite loop)

Win7 SP1 (64)
i7-3930K CPU@ 3.20GHz
32MB RAM


5-11-2013 16:18:46 World Community Grid task BETA_BETA_9999984_0946a_2 aborted by user
5-11-2013 16:18:46 World Community Grid task BETA_BETA_9999980_0075_2 aborted by user
5-11-2013 16:18:46 World Community Grid task BETA_BETA_9999981_0183_2 aborted by user
5-11-2013 16:19:30 World Community Grid [error] garbage_collect(); still have active task for acked result BETA_BETA_9999984_0946a_2; state 5
5-11-2013 16:19:30 World Community Grid [error] garbage_collect(); still have active task for acked result BETA_BETA_9999980_0075_2; state 5
5-11-2013 16:19:30 World Community Grid [error] garbage_collect(); still have active task for acked result BETA_BETA_9999981_0183_2; state 5
5-11-2013 16:19:31 World Community Grid Computation for task BETA_BETA_9999984_0946a_2 finished
5-11-2013 16:19:31 World Community Grid Computation for task BETA_BETA_9999980_0075_2 finished
5-11-2013 16:19:31 World Community Grid Computation for task BETA_BETA_9999981_0183_2 finished
----------------------------------------
[Edit 2 times, last edit by Former Member at Nov 5, 2013 3:29:45 PM]
[Nov 5, 2013 3:18:00 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: New Beta Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21

received 6 of which 3 valid and 3 pv
windows 7 i5 2600
32mb ram
[Nov 5, 2013 3:21:13 PM]   Link   Report threatening or abusive post: please login first  Go to top 
kateiacy
Veteran Cruncher
USA
Joined: Jan 23, 2010
Post Count: 1027
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test starting Nov 4, 2013 [ Issues Thread ] Version 7.21

I received 2, both on the same machine. They ran straight through with no issue, CPU time and elapsed time identical, and both validated.

Ubuntu 13.04
AMD Phenom II X4 910e processor
BOINC set to use 100% of CPU
----------------------------------------

[Nov 5, 2013 3:36:23 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 152   Pages: 16   [ Previous Page | 7 8 9 10 11 12 13 14 15 16 | Next Page ]
[ Jump to Last Post ]
Post new Thread