Changes between Version 3 and Version 4 of TestingProfiling

Timestamp:

03/18/10 16:44:51 (12 years ago)

Author:

cotto

Comment:

--

TestingProfiling

@@ -3 +3 @@
 == Issues ==
 
-=== randomness from timing information ===
+=== randomness from timing information (solved) ===
 A profile will contain a randomness in the form of timing information.  It does not make sense to test for absolute values since tests must be able to succeed on slow machines as well as fast.  It may make sense to test relative timing information, but even this is questionable.
 The best approach may be to enable the runcore to emit a canonical form of the profile in which all data that vary between runs (timing information, memory addresses) would be changed to constants.  This would also allow testing that times were added correctly and would simplify sanity checking.
+Note: This problem seems to be solved.  See docs/dev/profiling.pod for the solution to timing randomness and control flow differences due to hash seed randomization.
 
 === data volume ===