MathGroup Archive 1999

[Date Index] [Thread Index] [Author Index]

Search the Archive

Timing[] and AbsoluteTime[].

  • To: mathgroup at
  • Subject: [mg20257] Timing[] and AbsoluteTime[].
  • From: Guilherme Roschke <gr at>
  • Date: Sun, 10 Oct 1999 00:04:08 -0400
  • Organization: University of Pennsylvania
  • Sender: owner-wri-mathgroup at

How does timing measure its "value"?

here is my problem.  I have fuction f[x], which does a few hundred


= {1770.60,Null}.


before=AbsoluteTime[];  (# of secs since 1/1/1900)

 = {1770.60,Null}



= 14,673.000

Timing is off by a factor of 10!

Note that this is on a DEC with 2 21264 500mhz Alpha chips, where nothing
else is running except for the system deamons (lpd, sendmail, xserver

This is especially disconcerting because the AbsoluteTime[] elapsed is
closer to a PII350 that I have than I would have hoped for in doing
numerics on the Alpha machine.

Does anyone have any thoughts of what might be going on?  On how I could
actually receive my answer in 1,700 rather than 14,000 seconds?

I'm using version 4 for Digital Unix.



Guilherme Roschke			 	*
Programmer/SysAdmin/Researcher			*
Dept. of Anesthesia				*
University of Pennsylvania Medical School	*
gr at			*

  • Prev by Date: vector pattern?
  • Next by Date: Re: Finding lengths of identical sequences in lists
  • Previous by thread: Re: vector pattern?
  • Next by thread: Re: Timing[] and AbsoluteTime[].