Documentation for experimental branches, spikes, WIPs etc. You can also add documentation related to your merge requests or patches here.
The docs should be moved to proper place in OTS wiki after the feature gets integrated to master branch.
This area is relevant for OTS developers only! Information under this area does not apply to master or released OTS versions.
We have monitor DTO:s. Probably some kind of hierarchy of dto monitor objects.
What about statistics monitoring? What do we need?
Current implementation uses the same testrun response queue and process for monitor dto:s. This is simple to implement for testrun related events but very limited for generic monitoring of the whole system. For example most of the worker events cannot be sent to testrun queue because they are not related to a specific testrun and we don't know if there even is any testrun response queues around.
Having a separate permanent queue and a separate listener process for monitoring would allow monitoring also outside a testrun.
Tested with sqlite and MySQL
It looks like that MySQL does some caching because when a page is loaded for the first time it takes much longer to render the data than on following loads.
This means that on fixed time frame the pages can be loaded quite quickly, but when the time frame changes then the page loading takes more time.
200000 testruns and 1160443 events within fixed time frame average page loading time:
200000 testruns and 1160443 events within dynamic time frame:
1000 testruns and 5802 events average page loading time: