Hi,
I had a vlar 08ja11af.25606.9883.3.12.69.vlar that was about 50% completed after 15 hours and aborted it as abnormal. I am doing my runs, CPU only, on a dual core Intel E4700 processor and the vlars normally take around 6 hours (the estimate at the start was 5h 55m). I would have put it down to experience (or lack of it) but the next wu 08ja11af.25606.9883.3.12.54.vlar_0 is still running after 13h 25min showing 2 hours still to go.
My question is, is this normal for this series of vlars or is it a bad run or do I have something wrong with my wee processor.
I will not abort this run but let it go to completion and see what the result is.

I would appreciate any comments on how others are getting on with this vlar series or any similar experiences in the past.

Thanks
John

I have had tasks get 'stuck' before, a suspend/resume usually kicks them back in.

---

08ja11af.25606.9883.3.12.54.vlar_0 has completed and validated. 52,287 secs runtime and 21,318 cpu time.
I am at a loss to know why this disparity as I am not watching movies or playing games on the pc. I have looked at the Task manager and there isn't anything obvious running and I run Malwarebytes Threat scan and MS Security Essentials once a day.

I have rebooted to see if that makes a difference.

All suggestions appreciated.

Thanks
John

VLAR, depending on the angle, always took a lot longer than normal CPU work units.

It also depends on the type of CPU crunching the work units.

Intels tend to be "faster" than AMD chips.

VLAR work units were restricted to CPU after it was found they caused older GPUs to lock up or crash.

One of the others can explain how the angle determines how complex the calculations.

It must have been an odd WU as the rest of the vlars seem to be calculating at a reasonable time c6 hours. Either that or something went wrong with my wee pc. Either way I will keep a look out and report back here if it happens again.

Thanks
John

John i have had units take up to 19 hrs most will finish in a lot less but you will get the odd vlar that will take a long time all normal .

Worry only if after many hours it still says the same % done and the estimate time has not dropped but the time taken continues to go up . Then you can say it may be stuck and if after a restart there is no improvement abort it .

---

08ja11af.25606.9883.3.12.54.vlar_0 has completed and validated. 52,287 secs runtime and 21,318 cpu time.

Means it has run the normal 6 hours, but in the same time something else was eating up over 50% of your CPU cycles.

---