| 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: 20
|
|
| Author |
|
|
Byteball_730a2960
Senior Cruncher Joined: Oct 29, 2010 Post Count: 318 Status: Offline Project Badges:
|
Lawrence - I only have 2Gb of ram which is soldered to the motherboard, so I can't increase it.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello vcd683s,
2 GB RAM is plenty for 2 MCM jobs. I assume that you are getting your checkpoint data from BOINC Manager - Tasks - (select work unit) - Properties. What CPU percentage does Task Manager show for your work units? Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I can confirm the long runs on 946_3499_1 (24 hours so far, 83%), 946_3555_0 (19 hours so far, 52%), 955_7148_1 (18 hrs, 44.6%), 958_9659_1 (11 hrs, 16%).
Too bad I'm close to the deadline but I don't want to drop 60 hrs of work. I have i2520M on Linux. |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7849 Status: Offline Project Badges:
|
The average time per WU has been increasing of late. Here is a quick chart of the average time per WU for each date. Since the average time is increasing, there are probably some long units in there.
----------------------------------------![]() Cheers
Sgt. Joe
----------------------------------------*Minnesota Crunchers* [Edit 4 times, last edit by Sgt.Joe at Jan 3, 2014 3:17:12 AM] |
||
|
|
E. Frijters
Senior Cruncher The Netherlands Joined: Apr 26, 2007 Post Count: 228 Status: Offline Project Badges:
|
Some WU's are aborted because of the prolonged workload...
----------------------------------------3-1-2014 11:12:24 | World Community Grid | Aborting task MCM1_0000968_4106_0; not started and deadline has passed 3-1-2014 11:12:24 | World Community Grid | Aborting task MCM1_0000968_4490_1; not started and deadline has passed 3-1-2014 11:12:24 | World Community Grid | Aborting task MCM1_0000968_4583_1; not started and deadline has passed 3-1-2014 11:13:20 | World Community Grid | Sending scheduler request: To report completed tasks. 3-1-2014 11:13:20 | World Community Grid | Reporting 3 completed tasks 3-1-2014 11:13:20 | World Community Grid | Not requesting tasks: don't need 3-1-2014 11:13:23 | World Community Grid | Scheduler request completed 3-1-2014 11:24:15 | World Community Grid | Aborting task MCM1_0000968_1034_1; not started and deadline has passed 3-1-2014 11:24:15 | World Community Grid | Aborting task MCM1_0000968_1886_1; not started and deadline has passed
Former grid.org slave
![]() ![]() |
||
|
|
martianmoons
Cruncher USA Joined: Nov 29, 2006 Post Count: 49 Status: Offline Project Badges:
|
Some WU's are aborted because of the prolonged workload... Do the work units that need to get sent out again get sent out to more reliable and/or faster hosts? Would seem to make sense. [Edit 1 times, last edit by martianmoons at Jan 3, 2014 9:07:31 PM] |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7849 Status: Offline Project Badges:
|
Some WU's are aborted because of the prolonged workload... Do the work units that need to get sent out again get sent out to more reliable and/or faster hosts? Would seem to make sense. The short answer is yes. In order to complete the two units, an additional one will be sent out to a new host which has been deemed to be reliable. It will have a shorter deadline - 3 days I think. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
E. Frijters
Senior Cruncher The Netherlands Joined: Apr 26, 2007 Post Count: 228 Status: Offline Project Badges:
|
I don't think you get the point. Normally I do not have WU's that abort because of passed deadlines. The scheduler is probably too optimistic. This is the first time that this is happening...
----------------------------------------
Former grid.org slave
![]() ![]() |
||
|
|
ThreadRipper
Veteran Cruncher Sweden Joined: Apr 26, 2007 Post Count: 1324 Status: Offline Project Badges:
|
I see in my results status page that I have an MCM WU:
----------------------------------------MCM1_ 0001108_ 2807_ 1-- which ran 23.99 hours, but the Claimed credit was only 87.4 (!) That is Very low. It's a Core i3 CPU which usually scores much much higher that that. ![]() Join The International Team: https://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=CK9RP1BKX1 AMD TR2990WX @ PBO, 64GB Quad 3200MHz 14-17-17-17-1T, RX6900XT @ Stock AMD 3800X @ PBO AMD 2700X @ 4GHz |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7849 Status: Offline Project Badges:
|
I don't think you get the point. Normally I do not have WU's that abort because of passed deadlines. The scheduler is probably too optimistic. This is the first time that this is happening... Yes, I got the point that the machine was overscheduled, probably due to the variable length nature of the MCM1 project work units. Whatever the cache setting was could have been a contributing factor if the cache was set to more than 4 or 5 days. However I only tried to answer the question which was posed about the reissue of work units. Due to the sometimes highly variable nature of the length of these work units, in my humble opinion, I would not set my cache for more than 2 days. For instance on one of my crunchers, which is solely dedicated to WCG, the work units have varied from only a couple of hours to over 20 hours. If your cache is too large and your machine runs into a batch which takes 5 to 10 times longer than anticipated, you will run over the deadline with some units. However, all that being said, those work units will simply be re-issued to other machines and will get completed on a new schedule. Not to worry, these kind of little blips in the system are easily handled. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
|