[DGD] change in tick accounting

[Dread Quixadhal]

Interesting.

One assumes code that checks for resource limits will ask how much is left and then decide to keep running or continue in a new call_out(), so the net result should just be some code gets to run a little longer before it does that.  Runaway loops will still be caught nicely after a few extra iterations. 😊

The only thing it may impact is profiling via eval cost, since 2 chunks of code that don’t loop will now return the same values, even if one is quite a bit longer.  Unless you added in an estimate, like the number of instructions times a constant, perhaps?

Sent from Mail for Windows 10

From: Felix A. Croes
Sent: Sunday, June 24, 2018 2:18
To: dgd at dworkin.nl
Subject: [DGD] change in tick accounting

I have changed tick counting in DGD to add ticks for loops, rather than
for every instruction.  This will mean a global speedup, and makes it
easier to get the same tick count for JIT-compiled code, but existing
code will now use an overall lower amount of ticks than before.

Regards,
Felix Croes
____________________________________________
https://mail.dworkin.nl/mailman/listinfo/dgd