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: 3
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 31 times and has 2 replies
crosend
Cruncher
Joined: Mar 8, 2006
Post Count: 1
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Having to about tasks

I have noticed that I'm receiving World Community Tasks (Mapping Cancer Markers) that will never meet the deadline set. For example, one task has been running for 16 hours with 75 days remaining. Deadline was today, 12/5/25. My PC is Processor: Intel(R) Core(TM) i5-14500, with 15GB useable, with 14 cores. Do I abort them, or lets them run forever?
[Dec 6, 2025 12:27:45 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sgt.Joe
Ace Cruncher
USA
Joined: Jul 4, 2006
Post Count: 7844
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Having to about tasks

I would monitor their progress and see how fast they are progressing. If their pace is glacial, I would abort them. Then I would examine what else was using up cycles on my machine. Are there any background tasks using most of the processing power ??I might also cut back the number of concurrent work units I am running and see if they then progress satisfactorily.

Cheers
----------------------------------------
Sgt. Joe
*Minnesota Crunchers*
[Dec 6, 2025 2:16:22 AM]   Link   Report threatening or abusive post: please login first  Go to top 
alanb1951
Veteran Cruncher
Joined: Jan 20, 2006
Post Count: 1317
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Having to about tasks

There might be something relevant in the MCM asks not getting enough time and getting aborted thread in this forum.

Remember that WCG doesn't expose anything about your computer(s) so any help you get here will be dependent on how much we know - that's one of the things mentioned in the first reply in that thread, and once we got more information...

By the way, something that didn't get a serious mention in that thread is that MCM1 might repeatedly restart the application if it doesn't get through initialization within a given elapsed time -- that's one of the reasons for stressing that it's not a good idea to limit CPU time rather than limiting numbers of cores...

Good luck getting it sorted out.

Cheers - Al.
[Dec 6, 2025 6:01:33 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread