Nearly 100 of these arrived with an estimated run time of 1.5 to 3.5 hrs. These can usually be done within the deadline. So far, some of the tasks take up to 18 hrs on an 8 thread machine. Non have been within the "estimated" time....

Is this normal ??. With the machine also doing other projects some of the mw w/u will miss the deadlines

From what I see of it sometimes the estimated runtimes are way out ,
Though I only keep a very small cache of work here @home so never get past the deadlines .

In the end some 70+ jobs were cancelled due to the end date. Shame the jobs dident arrive with a more realistic run length. I know I could change the amount of work to store, but other projects get it about right...... usually.

In the end some 70+ jobs were cancelled due to the end date. Shame the jobs dident arrive with a more realistic run length. I know I could change the amount of work to store, but other projects get it about right...... usually.

They said the earlier tasks in a run take longer than the end of the run tasks, I think we are still in the early stages of this run. The run is a snapshot of an area they are looking to find something in, the early tasks have alot of 'stuff' to find so they take longer than the tasks at the end of the run where generally speaking there is little 'to see'.

With the machine also doing other projects some of the mw w/u will miss the deadlines

For the future simply reduce your cache. The more projects you run on a single machine, the lower your setting should be as the chance of running out of work decreases with every active project (and you can also set up one or more backup projects).

---