world.map_cpu is rounded to increments of 0.125

ID:2652496
 
Feb 2 2021, 3:34 pm
Resolved
Limitations in the timers used to measure tick usage meant that world.cpu, world.tick_usage, and world.map_cpu weren't very precise. These have been updated to be much more precise.
BYOND Version:514
Operating System:Windows 10 Home 64-bit
Web Browser:Chrome 87.0.4280.141
Applies to:Dream Daemon
Status: Resolved (514.1546)
This issue has been resolved.
Descriptive Problem Summary:
its hard to test SendMaps() cost when the result is rounded. Im trying to use a blank test template filled with a single turf type as a benchmark for every other test involving map_cpu, but its unusable for this purpose since it fluctuates between 0 and 0.125.

https://imgur.com/a/fJ07MNf
ran this test for 10 hours yesterday

Workarounds:
None, there is no workaround using in-engine methods for measuring SendMaps() cost



Feb 8 2021, 2:46 pm
Lummox JR resolved issue with message:
Limitations in the timers used to measure tick usage meant that world.cpu, world.tick_usage, and world.map_cpu weren't very precise. These have been updated to be much more precise.