A performance test for showing different ways of rendering the map to the screen
5
Small optimization tests (@ instead of peek, use of locals), and a tline approach that costs double the map() price, but has a lot of flexibility like 90° rotation, flip, 50% zoom ... at no extra CPU cost.
If the timing to get stat(1) is after print, the difference in length of the description would affect the CPU usage display.
[Please log in to post a comment]
