Message boards :
Theory Application :
Theory native - Runtime Pitfall
Message board moderation
| Author | Message |
|---|---|
 Send message Joined: 28 Jul 16 Posts: 473 Credit: 389,411 RAC: 77   |
The different runtimes of the scientific apps most likely cause a pitfall regarding the use in a production environment, especially if volunteers also participate in other projects. Reason Out of experience (e.g. SixTrack) we know that variable runtimes/CPU-times do not only result in credit variations (much too low <--> much too high). They also result in a wrong runtime estimation. This is a minor problem if the estimated runtime is too long as the BOINC client would simply request fewer tasks. It could become a major problem if the estimated runtime is far too low as the BOINC client would request lots of tasks that will hardly/never meet their due dates or block other tasks/projects. Measure As the <rsc_fpops_est> value is a major factor used to calculate the estimated runtime, this value must be set by the server as precise as possible. This has to be done individually for each scientific app, e.g. Herwig, Pythia, Sherpa ... |
 Laurence Send message Joined: 12 Sep 14 Posts: 1064 Credit: 325,950 RAC: 42 |
This should be possible. |
|
Laurence Send message Joined: 12 Sep 14 Posts: 1064 Credit: 325,950 RAC: 42 |
Just for reference, here is a list of job types that I found. epos herwig++ herwig7 herwig++powheg madgraph5amc phojet pythia6 pythia8 sherpa vincia |
|
Send message Joined: 28 Jul 16 Posts: 473 Credit: 389,411 RAC: 77 |
Just for reference, here is a list of job types that I found. agile-runmc?? It's currently running on one of my VMs. |
|
Send message Joined: 22 Apr 16 Posts: 664 Credit: 1,791,095 RAC: 4,208 
|
|
|
Send message Joined: 13 Feb 15 Posts: 1179 Credit: 815,336 RAC: 580 |
What happens when one catch an endless running Sherpa job? Will it be killed after xx hours runtime? -- without granting credits ;-( |
©2024 CERN