-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
us-east-2 (Ohio) -- > us-east-1 (N. Virginia) ~10ms #78
Comments
@alexsnaps interesting to note that ping is about 10ms (done with This is maybe because we are doing two RTT (one for read counters, other for writting)?? |
Noting also that this setup is unconventional, we then might want to run the same test when we have setup using Transit Gateways |
Yes... there are multiple roundtrips to Redis... added to that, there is the work redis has to do, encoding/decoding the requests, serializing/deserializing the payloads... I get it that the latter are CPU bound and not necessarily affected by the network... tho we are still not as lightweight as a
|
Adding this new test for the record: 3 limts ---
- namespace: test_namespace
max_value: 100000
seconds: 5
conditions:
variables:
- namespace: test_namespace
max_value: 100000
seconds: 4
conditions:
variables:
- namespace: test_namespace
max_value: 100000
seconds: 3
conditions:
variables: When there is 1 limit, limitador needs 1 RTT to get all the counter values and 1 RTT to increment. Total 2*RTT. When there are 3 limit, limitador needs 1 RTT to get all the counter values and 3 RTT to increment them. Total 4*RTT. Result
The latency is x2 as expected |
Adding this new test for the record: redis cache with defaults
Latency is 1 RTT (10ms ping) |
Adding this new test for the record: redis cache with
Latency is 0 RTT (jitter 1RTT for read and 2 RTT for read+write) |
Adding this new test for the record:
I do not notice any difference regarding the first test without the rate limit response headers |
Test setup
Redis proxy
1 EC2 instance
us-east-1 (N. Virginia)
AZ: us-east-1a
amazon linux 2023 AMI
type: c7i.large 2vCPU 4Gib Memory
Elasticache
Limtador and Driver
1 EC2 instance
eu-east-2 (Ohio)
AZ: eu-north-1c
amazon linux 2023 AMI
type: c7i xlarge 4vCPU 8Gib Memory
sudo yum update -y sudo yum install -y docker sudo service docker start sudo usermod -a -G docker ec2-user # (logout and login again) docker ps
Limits designed to never hit the threshold, so all requests increment the counter.
Results
The text was updated successfully, but these errors were encountered: