hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Lower throttling limit in mxs173_throttle_filter

Browse Source 
The test appears to fail when the throttling is unable to keep the QPS
high enough for the test to pass. To reduce the likelihood of this, lower
the limit to 500 QPS.

In theory, the minimum delay of one millisecond in the delayed_call limits
the filter to a maximum QPS of 1000 as each query would wait for at least
a millisecond before being routed. This is yet to be proven but it would
explain why the tests are having a hard time approaching that level of
QPS.
This commit is contained in:
Markus Mäkelä 2019-07-01 17:26:17 +03:00
parent 25d134df9c
commit 6b11067690
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
maxscale-system-test/cnf/maxscale.cnf.template.mxs173_throttle_filter
View File

@ -56,7 +56,7 @@ port = 4009
[throttle]
type = filter
module = throttlefilter
max_qps = 1000
max_qps = 500
throttling_duration = 10000
sampling_duration = 250
continuous_duration = 2000

2
maxscale-system-test/mxs173_throttle_filter.cpp
View File

@ -15,7 +15,7 @@ DEFINE_EXCEPTION(Whoopsy);
// TODO these should be read from maxscale.cnf. Maybe the test-lib should replace
// any "###ENV_VAR###", with environment variables so that code and conf can share.
constexpr int max_qps = 1000;
constexpr int max_qps = 500;
constexpr float throttling_duration = 10000 / 1000.0;
constexpr float sampling_duration = 250 / 1000.0;
constexpr float continuous_duration = 2000 / 1000.0;