[MXS-4848] Replace timing measurements in idle_pool_max_conns Created: 2023-11-02  Updated: 2023-12-18

Status: Stalled
Project: MariaDB MaxScale
Component/s: test
Affects Version/s: 6.4, 22.08, 23.02, 23.08
Fix Version/s: 6.4

Type: Task Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Unresolved Votes: 0
Labels: None

Sprint: MXS-SPRINT-196, MXS-SPRINT-197

 Description   

The test uses hard-coded time limits to evaluate whether queries are being served on time. This has shown to not be a reliable way of measuring how well the feature is working and it keeps failing. Something other than the time it takes to run all queries need to be used as the metric, potentially per query latencies to see how fair the scheduling is.



 Comments   
Comment by markus makela [ 2023-12-18 ]

So far we've yet to find a meaningful metric that can be measured in a consistent manner.

Generated at Thu Feb 08 04:31:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.