Tags: , ,

Whether you’re using Adobe Scout or good old getTimer, there is a fundamental limitation: all times are in whole milliseconds. This is an issue if you’re trying to measure code that executes very quickly or compare code that has only minor differences. In these cases you get inconsistent results (7ms, 8ms, 7ms, 7ms, 8ms, …) when you’d much rather have better accuracy (7.3ms) with sub-millisecond precision. Today’s article introduces a new helper class called Timely that makes sub-millisecond precision a snap. Read on for the source code and an example app.

Read the rest of this article »