Reimar Grabowski :
> > If you want to get better than that, you need to get system specific,
> > I'm afraid.
>
> That's not true. As Graeme already mentioned there is EpikTimer which is
> a cross-plattform, high-resolution timer (which btw works very well for
> realtime tasks).
Well, that depends
> If you want to get better than that, you need to get system specific, I'm
> afraid.
That's not true. As Graeme already mentioned there is EpikTimer which is a
cross-plattform, high-resolution timer (which btw works very well for realtime
tasks).
R.
--
A: Because it messes up the order in w
> The standard clock for the system timer runs at 1,193,182 Hz, derived
> for the original IBM PC as the 4.77 MHz processor clock divided by 4.
Digging a bit deeper clarifies it:
http://sos.enix.org/lxr/source/hwcore/i8254.c?v=6.5
|* Ahhh PC systems are nice toys: this maximum "strange" freque
> On Tue, 01 Jun 2010 19:58:54 +0200
> "Vinzent Höfler" wrote:
>
> > "spir ☣" :
> >
> > > Thank you. Using dos.getTime (including its last arg), the following
> > > returns integer time in 10^-2s units:
> > [...]
> > >
> > > This is the needed base for my uses. (A unit of 1s is too gross for
>
Thank you for this precision. Where does getTime actually get its time? And
where do these numbers come from; I mean why chose this time unit instead of
plain 1/10 or 1/100 or 1/1000s? (1193182 does not look familiar to my eyes ;-)
Do you have an idea on how to get one of those time units (ms wo
On Tue, 01 Jun 2010 19:58:54 +0200
"Vinzent Höfler" wrote:
> "spir ☣" :
>
> > Thank you. Using dos.getTime (including its last arg), the following
> > returns integer time in 10^-2s units:
> [...]
> >
> > This is the needed base for my uses. (A unit of 1s is too gross for
> > timing, this leads
"spir ☣" :
> Thank you. Using dos.getTime (including its last arg), the following
> returns integer time in 10^-2s units:
[...]
>
> This is the needed base for my uses. (A unit of 1s is too gross for
> timing, this leads to endless runs; more precision than 10^-2s is
> unneeded.)
Actually, the r
On Tue, 18 May 2010 10:47:33 +0200 (CEST)
"Tomas Hajny" wrote:
> On Mon, May 17, 2010 22:25, spir ☣ wrote:
>
>
> Hello Denis,
>
> > I posted a question about timing some time a go and got an answer; but let
> > down for a while because other problems required my attention. So, I need
> > a s
On Mon, May 17, 2010 22:25, spir ⣠wrote:
Hello Denis,
> I posted a question about timing some time a go and got an answer; but let
> down for a while because other problems required my attention. So, I need
> a simple func to get the current time; mainly to benchmark various
> implementation
Felipe Monteiro de Carvalho het geskryf:
> You can use EpikTimer for that:
>
> http://wiki.lazarus.freepascal.org/EpikTimer
>
Included in the lazarus-ccr bug report is the patch that splits the
EpikTimer package into Runtime and Designtime packages. Could you apply
this to Lazarus-CCR please.
spir ☣ het geskryf:
> let down for a while because other problems required my attention. So, I
> need a simple func to get the current time; mainly to benchmark various
> implementation choices, possibly for other needs.
A very crude solution would be to use Sysutils.GetTickCount() before and
afte
You can use EpikTimer for that:
http://wiki.lazarus.freepascal.org/EpikTimer
--
Felipe Monteiro de Carvalho
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Hello,
I posted a question about timing some time a go and got an answer; but let down
for a while because other problems required my attention. So, I need a simple
func to get the current time; mainly to benchmark various implementation
choices, possibly for other needs.
The timer module brin
13 matches
Mail list logo
