Can someone confirm this please? If it is not true, something very strange is going on. Three tasks from the same batch of the testing branch of my main project, two on a desktop that is older and slower than the laptop that has the other. The two on the desktop started seven minutes earlier than the one on the laptop yet the one on the laptop is currently showing 45 minutes elapsed time against 31 minutes elapsed time for the two on the desktop, which has been getting light use (browsing and word processing) throughout. May or may not be relevant that the laptop is using WINE for BOINC and the desktop native Linux.

Not a biggie in the grand scheme of things but interesting to know.

No, CPU time is CPU time, Elapsed time is system clock time.

---

No, CPU time is CPU time, Elapsed time is system clock time.

Thanks for that.

Which makes me wonder why does the elapsed time on the two tasks running under Linux show an elapsed time of about one and a half hours when there has been almost two and a half hours since the task started, machine running continuously since tasks started. Will check to see if the same happens under WINE on this machine but that will have to wait till the two tasks running are finished.

Edit: The logical conclusion is that the two tasks on the desktop machine aren't computing all the time. I just need to think of a way to check this out. - whenever I run top the processes show as using nearly all the cpu time so I guess I need to get more inventive about how I look.

As a post script to this question I have learned that there are some of the CPDN tasks that seem to reset the CPU time and cause massive discrepancies between CPU time and elapsed time. Seems I must have had one of these tasks. (Most of the tasks that have this large discrepancy are ones that fail.)