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 750 times and has 2 replies Next Thread
Randzo
Senior Cruncher
Slovakia
Joined: Jan 10, 2008
Post Count: 339
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
12 hour cutoff limit is cutting the large task too early (even before completion of crucial 2.nd task)

just one sad think that I noticed.
Now when we are running large molecules on the grid sometimes happen that they are cutoff too early.
I can see that the last checkpoint was 20.st or 30.st minute of the work unit run it is running till 12 hour minute and than it is cut off so we loose 11:30 hours of run time and probably the work unit isn't very useful for the researchers when the most important task No. 2 is not finished.

Any thoughts on this, for example to cut off the work units after 12 hours of run time only after task 2 has been successfully completed?
[Sep 17, 2013 4:05:15 PM]   Link   Report threatening or abusive post: please login first  Go to top 
littlepeaks
Veteran Cruncher
USA
Joined: Apr 28, 2007
Post Count: 748
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 12 hour cutoff limit is cutting the large task too early (even before completion of crucial 2.nd task)

This is not an answer to your question, but think we are now getting some WUs with super long run times. For the first time on this PC, I exceeded the 12 hour run time which caused job #11 to be cutoff because the runtime was exceeded -- and this PC is fairly speedy.

Result Name: E215531_ 254_C.39.C32H18N2OS2Si2.00696802.3.set1d06_ 0--
Look at the time for the second task -- almost 8 hours.

[08:16:24] Number of jobs = 16
[08:16:24] Starting job 0,CPU time has been restored to 0.000000.
[08:20:25] Finished Job #0
[08:20:25] Starting job 1,CPU time has been restored to 205.250516.
[08:33:15] Finished Job #1
[08:33:15] Starting job 2,CPU time has been restored to 971.402627.
[16:01:11] Finished Job #2

Just noticed I was assigned a wingman, who was cutoff during task 2 because runtime was exceeded.

BTW, these longer WUs are intemixed with shorter ones.

Edited for clarification.
----------------------------------------
[Edit 1 times, last edit by littlepeaks at Sep 18, 2013 2:21:25 PM]
[Sep 17, 2013 9:37:56 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: 12 hour cutoff limit is cutting the large task too early (even before completion of crucial 2.nd task)

Plz post a copy-paste of the Result Status page record that displays there was more than 12.01 CPU time for the CEP2 job [Runtime not of interest as this is reflective of the host efficiency versus CPU time for CPU only jobs.]
[Sep 18, 2013 12:10:33 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread