Changes between Version 21 and Version 22 of GhciDebugger

Timestamp:

02/20/07 06:08:44 (6 years ago)

Author:

mnislaih

Comment:

Yay! Overhead is down to 2.6x

GhciDebugger

@@ -264 +264 @@
 == Overhead ==
 The instrumentation scheme potentially introduces overhead at two stages: compile-time and run-time. Compile-time overhead is unnoticeable for general programs, although there are no benchmarks available to sustain this claim. Run-time overhead is much more noticeable.
-Run-time overhead has been measured informally to range in between 9x and 25x, depending on the code of the program under consideration. 
+Run-time overhead has been measured informally to range in between 9x and 25x, depending on the code of the program under consideration.  '''This is no longer true. ''' After extensive benchmarking and tweaking, overhead is down to 166% in average, 560% worst case, measured over the entire nofib suite.
+
 
 With an always-on breakpoints scenario in mind, we do a number of things to mitigate this overhead in absence of enabled breakpoints. One of these is to allow a ghc-api client to disable auto breakpoints via the ghc-api functions: