You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have conducted an analysis of the request-rate and interval variables in the benchmarking_script.py and would like to ensure that my understanding is correct.
My understanding is that the request-rate parameter introduces delays between each request to mimic the queries-per-second (QPS) rate. For example, if it is set to 5, then 5 requests are sent within a 1-second window for a sufficiently large number of samples.
That being said, the delay implementation generates random delay values with slightly high variance, but the average is fairly consistent:
I have conducted an analysis of the
request-rate
andinterval
variables in thebenchmarking_script.py
and would like to ensure that my understanding is correct.My understanding is that the
request-rate
parameter introduces delays between each request to mimic thequeries-per-second
(QPS
) rate. For example, if it is set to 5, then 5 requests are sent within a 1-second window for a sufficiently large number of samples.That being said, the delay implementation generates random delay values with slightly high variance, but the average is fairly consistent:
interval = np.random.exponential(1.0 / request_rate)
The graph of
exponential distribution
from which1/request-rate
is being sampledWhen I plot the
interval
values for a given request-rate (e.g., 5), I get the following plot after running it 1000 times:With these statistics:
Given that the mean is around 0.2, the overall QPS is 5 requests per second (since 5 × 0.2 = 1 second).
Here are the statistics for
request-rate = 10
:In conclusion, the
request-rate
parameter effectively mimics the QPS (queries per second) metric when the number of samples is large enough.I would like to confirm that my understanding is correct and document this in the issues section for anyone else who might have the same question.
The text was updated successfully, but these errors were encountered: