Re: Timing
From: Malek (kemmou_at_arrabeta.com)
Date: 02/23/04
- Next message: John Baro: "Re: Drawing shaded lines and shapes"
- Previous message: fbhcah: "RE: Datagrid crashes program, when input data is too large"
- In reply to: Malek: "Re: Timing"
- Next in thread: Shawn B.: "Re: Timing"
- Reply: Shawn B.: "Re: Timing"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 23 Feb 2004 04:30:10 -0000
Sorry, I am flatly wrong ... if you do control your cycles, at the speed you
are talking about, Richard is totally right ... a timer uses ticks, and will
not be slowed down... with time slicing, you can be pretty sure that you are
not getting any real delays to your execution..
"Malek" <kemmou@arrabeta.com> wrote in message
news:eYuzaPc%23DHA.2824@tk2msftngp13.phx.gbl...
> using a timer would seem a good option for slowing down the execution,
> however, the equation 1/speed is not good unless you can consider the
> execution of your code and anything else hapening on the machine to be
> indignificant ... I would benchmark to see how accurate that assertion is,
> and would adjust accordingly... maybe using some performance counters on
the
> process could help on the benchmark or could be added as adjusting factor
> during execution (to account for whatever else is going on on the machine
> that might slow your execution)
> "Richard Sadler" <ihaveaholeinmyarm@blueyonder.co.uk> wrote in message
> news:9E95FFFD-3907-43F0-BC7E-EADC55424457@microsoft.com...
> > Hey
> >
> > You could use a timer (System.Timers.Timer) and set the delay to 1 /
speed
> (so the time is in seconds) and then use the event to perform the next
> instruction on the processor.
>
>
- Next message: John Baro: "Re: Drawing shaded lines and shapes"
- Previous message: fbhcah: "RE: Datagrid crashes program, when input data is too large"
- In reply to: Malek: "Re: Timing"
- Next in thread: Shawn B.: "Re: Timing"
- Reply: Shawn B.: "Re: Timing"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|