|
Moving on to the computational costs, lets look at how path feasibility impacts our Juliet test suite benchmarks.
In terms of speed, we see a 10% time overhead. The memory overhead is roughly 80%. While that might sound high at first glance, its important to remember that these percentages are relative to the Memory Leak Hunter performance. For this specific test suite, 80% is actually well within an acceptable range.
Furthermore, the process is highly scalable. If MLH identifies multiple issues, we can run the path feasibility analysis for each one in parallel. |