The article should incorporate the information that it is possible for wall clock time to be less than CPU time, namely when doing parallel computation on more
| The content of the Wall-clock time page was merged into Elapsed real time on 11 July 2017, and it now redirects there. For the contribution history and old versions of the merged article, please see its history. |
The article should incorporate the information that it is possible for wall clock time to be less than CPU time, namely when doing parallel computation on more than one CPU. Eriatarka (talk) 14:09, 6 March 2009 (UTC)
Should this artical also explain the time differences in a data processing context? A distinction is sometimes made between the time when the processing is actually performed (the Wall clock time ) versus when it should be done. Example: Each day a report must be made about orders completed the previous day. Due to a technical problem this was not done for several days. Later the the missing reports need to be generated. At that time the report generation will run as if it was a few days earlier - whereas the actual (wall clock time) time will be later. In particular, this applies to testing setups of such jobs. 193.191.180.231 (talk) 10:00, 10 August 2011 (UTC)
I often see wall time used to describe an entire business process, not just the computer part. As such it also includes delays incurred by the users themselves. The current article talks about programmed delays, and contrary to the variation described which excludes programmed delay, my experience includes user-delays. E.g.
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.