@antoine-daigneault-demers The logic of the test seems good and that's a pretty good idea to navigate to the next page as you did.
I've tested it out and it takes a good amount of time to load all of those 50 Chromedriver instances! Is it possible to add some logging telling use the progression, and/or have Chromedriver spanning up faster?
I see this benchmark as the initiator of the load test and being able to have a collector getting the metrics from this admin page (via the python package directly I think it's feasible, no screen scraping in here!) would be a winning combination.
On one hand we would have the "session starter", while on the other we would see how resources gets consumed via the "metrics collector".
Do you think it would be feasible to have these "admin page metrics" asserted in the test, so we can launch Holoviz Panel tests on any instance and get the performance results?
@antoine-daigneault-demers The logic of the test seems good and that's a pretty good idea to navigate to the next page as you did.
I've tested it out and it takes a good amount of time to load all of those 50 Chromedriver instances! Is it possible to add some logging telling use the progression, and/or have Chromedriver spanning up faster?
I see this benchmark as the initiator of the load test and being able to have a collector getting the metrics from this admin page (via the python package directly I think it's feasible, no screen scraping in here!) would be a winning combination.
On one hand we would have the "session starter", while on the other we would see how resources gets consumed via the "metrics collector".
Do you think it would be feasible to have these "admin page metrics" asserted in the test, so we can launch Holoviz Panel tests on any instance and get the performance results?