Re: CPU time versus wall clock time
From: Scott Kelly (scottjk_at_softhome.net)
Date: 10/30/03
- Next message: Jerry Coffin: "Re: C++ and input, it can't be platform specific"
- Previous message: Karl Heinz Buchegger: "Re: function x call function y call funtion x again ..."
- In reply to: Jerry Coffin: "Re: CPU time versus wall clock time"
- Next in thread: Martijn Lievaart: "Re: CPU time versus wall clock time"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 30 Oct 2003 13:15:54 GMT
On Thu, 30 Oct 2003 04:15:57 GMT, Jerry Coffin <jcoffin@taeus.com>
wrote:
>In article <80m0qvopu4cijkube7hv6tl385ep3h30uk@4ax.com>,
>scottjk@softhome.net says...
>
>[ ... ]
>
>> Considering I can't read C++ (yet), and yes, I'm a novice at C, that
>> didn't help. It just showed me that clock time and cpu time can
>> differ.
>
>It's only vaguely related to C or C++ (or any programming language per
>se) but the basic idea is pretty simple: clock time is often known as
>wall time -- it's the period of time taken from starting a task to
>finishing it.
>
>CPU time is only the amount of time that the CPU itself is actually
>working on your problem. It doesn't include things like waiting for
>data to be read in from the disk, or to come across a network, or time
>that the CPU is executing other tasks.
Thanks, Jerry! That cleared it right up! :)
- Next message: Jerry Coffin: "Re: C++ and input, it can't be platform specific"
- Previous message: Karl Heinz Buchegger: "Re: function x call function y call funtion x again ..."
- In reply to: Jerry Coffin: "Re: CPU time versus wall clock time"
- Next in thread: Martijn Lievaart: "Re: CPU time versus wall clock time"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
