Re: CPU time versus wall clock time
From: Jerry Coffin (jcoffin_at_taeus.com)
Date: 10/30/03
- Next message: Jerry Coffin: "Re: C++ and input, it can't be platform specific"
- Previous message: Micah Cowan: "Re: 0.1 = 0 ???"
- In reply to:(deleted message) Scott Kelly: "Re: CPU time versus wall clock time"
- Next in thread: Scott Kelly: "Re: CPU time versus wall clock time"
- Reply: Martijn Lievaart: "Re: CPU time versus wall clock time"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 30 Oct 2003 04:15:57 GMT
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.
--
Later,
Jerry.
The universe is a figment of its own imagination.
- Next message: Jerry Coffin: "Re: C++ and input, it can't be platform specific"
- Previous message: Micah Cowan: "Re: 0.1 = 0 ???"
- In reply to:(deleted message) Scott Kelly: "Re: CPU time versus wall clock time"
- Next in thread: Scott Kelly: "Re: CPU time versus wall clock time"
- Reply: Martijn Lievaart: "Re: CPU time versus wall clock time"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
