Unit testing your code's performance, part 1: Big-O scaling