Unclear link between perfomanceRequirementThreshold in config and results for Dynamic Spotter

[tormoseng]

In tests I set the perfomanceRequirementThreshold-parameter to 10.000 ms in the DynamicSpotter configuration. When the results come, the figures show a detected OLB for response times around 38 ms. The threshold is pictured to be at 17 ms. Howcome?

[jurepolutnik]

Added Chemnitz ppl to this task.

[tormoseng]

I ran a longer test yesterday evening with OLB at database scope, and there it actually seems that the threshold set in the configuration IS considered when finding problems. However, when the result is displayed, the threshold is pictured to be 17 ms. When I reported the issue, the test was done with OLB at entry scope - and the DynSpotter then discovered problems when the results was no higher than 38 ms. Might it be an issue that depends on the scope set + a clear issue with displaying the threshold.

[snowball77]

This sounds like a bug deep inside the OLB detector. This can take some time to understand the code. I haven't really looked into it so far...

[tormoseng]

I guess this is not time we have at them moment either. The evaluation should be wrapped up pretty soon. But as noted before, this is not a commercial product, but a product with great potential!