Re: os.clock() always return 0 on Archlinux (a Linode instance)

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

• Subject: Re: os.clock() always return 0 on Archlinux (a Linode instance)
• From: David Given <dg@...>
• Date: 2011年9月27日 20:14:31 +0100

---

On 27/09/11 18:01, Peter Cawley wrote:
[...]
> os.time - the current time ... or a time representing the date and
> time specified by the given table
Beware, though --- os.time() has a granularity of seconds, so making it
tricky to use for benchmarks. Hence my recommendation of
socket.gettime(), which doesn't.
Just out of interest, has anyone used os.clock() for *anything*, ever?
(Not counting Windows systems where it's equivalent to os.time().)
-- 
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ "Under communism, man exploits man. Under capitalism, it's just the
│ opposite." --- John Kenneth Galbrith

Attachment: signature.asc
Description: OpenPGP digital signature

---

• Follow-Ups:
  • Re: os.clock() always return 0 on Archlinux (a Linode instance), Rob Kendrick
  • Re: os.clock() always return 0 on Archlinux (a Linode instance), Luiz Henrique de Figueiredo
  • Re: os.clock() always return 0 on Archlinux (a Linode instance), Johnson Lin
  • Re: os.clock() always return 0 on Archlinux (a Linode instance), Stuart P. Bentley

• References:
  • os.clock() always return 0 on Archlinux (a Linode instance), Johnson Lin
  • Re: os.clock() always return 0 on Archlinux (a Linode instance), Peter Cawley

• Prev by Date: Re: os.clock() always return 0 on Archlinux (a Linode instance)
• Next by Date: Re: os.clock() always return 0 on Archlinux (a Linode instance)
• Previous by thread: Re: os.clock() always return 0 on Archlinux (a Linode instance)
• Next by thread: Re: os.clock() always return 0 on Archlinux (a Linode instance)
• Index(es):
  • Date
  • Thread