[DGD] Reasonable Tick Counts?

[Noah Gibbs]

  If you're going past 10,000 ticks then either you're processing something
absolutely huge, or you've got a serious coding error.

  A tick is a processor-independent measurement of execution time.  Since it's
not possible to do that perfectly, DGD assigns different operations different
'costs' in ticks in a way that is reasonably sensible on current hardware, and
adds them up as it executes.  The idea is that the number of ticks an operation
costs is meant to be roughly proportional to its cost in cycles on the
hardware, but that's not possible to do exactly in a processor-independent way.

  Since ticks are assigned approximately arbitrarily, you pretty much just need
to try some things and see how many ticks they take in order to get a feel for
that -- rather like processor cycles.

--- Kurt Nordstrom <kurt at blar.net> wrote:

> Been running into trouble lately with an "out of ticks" message in some
> code I have to parse codes into ansi escape sequences for use in
> communications.  Currently, I'm building off of a Melville base, and it
> sets the default maximum tick count to 100000.  The function I have that
> causes the overflow is a replace_str(str, original, new) function, that
> replaces all instances of "original" in "str" with "new".
> 
> Is it reasonable to have to expect to increase the tick count here, or is
> probably poor coding on my part?
> 
> And can anybody give me an idea of what a tick is anyhow?
> ___________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd
> 





       
____________________________________________________________________________________
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games.
http://sims.yahoo.com/