From e505a0796268ae773862b4d42be33b776867729c Mon Sep 17 00:00:00 2001 From: rishabhpoddar Date: Mon, 20 Nov 2023 11:39:53 +0530 Subject: [PATCH] changes to rate limit policy docs --- v2/emailpassword/rate-limits.mdx | 6 +++--- v2/passwordless/rate-limits.mdx | 6 +++--- v2/session/rate-limits.mdx | 6 +++--- v2/thirdparty/rate-limits.mdx | 6 +++--- v2/thirdpartyemailpassword/rate-limits.mdx | 6 +++--- v2/thirdpartypasswordless/rate-limits.mdx | 6 +++--- 6 files changed, 18 insertions(+), 18 deletions(-) diff --git a/v2/emailpassword/rate-limits.mdx b/v2/emailpassword/rate-limits.mdx index ad9801649..3dc530dfb 100644 --- a/v2/emailpassword/rate-limits.mdx +++ b/v2/emailpassword/rate-limits.mdx @@ -20,7 +20,7 @@ To know more about rps and bursts, please [this nginx document](https://www.ngin ::: ## Free tier -The free tier of the managed service has a rate limit of 10 requests per second with a burst of 20 requests per second (with nodelay). This should be enough for 2 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). +The free tier of the managed service has a rate limit of 25 requests per second with a burst of 25 requests per second (with nodelay). This should be enough for 5 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). :::important Our backend SDK auto retries if it gets a `429` status code from the core (up to 5 times before throwing an error). @@ -54,7 +54,7 @@ http { default $binary_remote_addr; } - limit_req_zone $limit_req_zone_key zone=mylimit:10m rate=10r/s; + limit_req_zone $limit_req_zone_key zone=mylimit:10m rate25/s; limit_req_status 429; # other configs.. @@ -64,7 +64,7 @@ http { } server { - limit_req zone=mylimit burst=20 nodelay; + limit_req zone=mylimit burst=25 nodelay; # other configs.. diff --git a/v2/passwordless/rate-limits.mdx b/v2/passwordless/rate-limits.mdx index 3b1db5865..e271596da 100644 --- a/v2/passwordless/rate-limits.mdx +++ b/v2/passwordless/rate-limits.mdx @@ -20,7 +20,7 @@ To know more about rps and bursts, please [this nginx document](https://www.ngin ::: ## Free tier -The free tier of the managed service has a rate limit of 10 requests per second with a burst of 20 requests per second (with nodelay). This should be enough for 2 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). +The free tier of the managed service has a rate limit of 25 requests per second with a burst of 25 requests per second (with nodelay). This should be enough for 5 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). :::important Our backend SDK auto retries if it gets a `429` status code from the core (up to 5 times before throwing an error). @@ -54,7 +54,7 @@ http { default $binary_remote_addr; } - limit_req_zone $limit_req_zone_key zone=mylimit:10m rate=10r/s; + limit_req_zone $limit_req_zone_key zone=mylimit:10m rate25/s; limit_req_status 429; # other configs.. @@ -64,7 +64,7 @@ http { } server { - limit_req zone=mylimit burst=20 nodelay; + limit_req zone=mylimit burst=25 nodelay; # other configs.. diff --git a/v2/session/rate-limits.mdx b/v2/session/rate-limits.mdx index 3b1db5865..e271596da 100644 --- a/v2/session/rate-limits.mdx +++ b/v2/session/rate-limits.mdx @@ -20,7 +20,7 @@ To know more about rps and bursts, please [this nginx document](https://www.ngin ::: ## Free tier -The free tier of the managed service has a rate limit of 10 requests per second with a burst of 20 requests per second (with nodelay). This should be enough for 2 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). +The free tier of the managed service has a rate limit of 25 requests per second with a burst of 25 requests per second (with nodelay). This should be enough for 5 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). :::important Our backend SDK auto retries if it gets a `429` status code from the core (up to 5 times before throwing an error). @@ -54,7 +54,7 @@ http { default $binary_remote_addr; } - limit_req_zone $limit_req_zone_key zone=mylimit:10m rate=10r/s; + limit_req_zone $limit_req_zone_key zone=mylimit:10m rate25/s; limit_req_status 429; # other configs.. @@ -64,7 +64,7 @@ http { } server { - limit_req zone=mylimit burst=20 nodelay; + limit_req zone=mylimit burst=25 nodelay; # other configs.. diff --git a/v2/thirdparty/rate-limits.mdx b/v2/thirdparty/rate-limits.mdx index 3b1db5865..e271596da 100644 --- a/v2/thirdparty/rate-limits.mdx +++ b/v2/thirdparty/rate-limits.mdx @@ -20,7 +20,7 @@ To know more about rps and bursts, please [this nginx document](https://www.ngin ::: ## Free tier -The free tier of the managed service has a rate limit of 10 requests per second with a burst of 20 requests per second (with nodelay). This should be enough for 2 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). +The free tier of the managed service has a rate limit of 25 requests per second with a burst of 25 requests per second (with nodelay). This should be enough for 5 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). :::important Our backend SDK auto retries if it gets a `429` status code from the core (up to 5 times before throwing an error). @@ -54,7 +54,7 @@ http { default $binary_remote_addr; } - limit_req_zone $limit_req_zone_key zone=mylimit:10m rate=10r/s; + limit_req_zone $limit_req_zone_key zone=mylimit:10m rate25/s; limit_req_status 429; # other configs.. @@ -64,7 +64,7 @@ http { } server { - limit_req zone=mylimit burst=20 nodelay; + limit_req zone=mylimit burst=25 nodelay; # other configs.. diff --git a/v2/thirdpartyemailpassword/rate-limits.mdx b/v2/thirdpartyemailpassword/rate-limits.mdx index 3b1db5865..e271596da 100644 --- a/v2/thirdpartyemailpassword/rate-limits.mdx +++ b/v2/thirdpartyemailpassword/rate-limits.mdx @@ -20,7 +20,7 @@ To know more about rps and bursts, please [this nginx document](https://www.ngin ::: ## Free tier -The free tier of the managed service has a rate limit of 10 requests per second with a burst of 20 requests per second (with nodelay). This should be enough for 2 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). +The free tier of the managed service has a rate limit of 25 requests per second with a burst of 25 requests per second (with nodelay). This should be enough for 5 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). :::important Our backend SDK auto retries if it gets a `429` status code from the core (up to 5 times before throwing an error). @@ -54,7 +54,7 @@ http { default $binary_remote_addr; } - limit_req_zone $limit_req_zone_key zone=mylimit:10m rate=10r/s; + limit_req_zone $limit_req_zone_key zone=mylimit:10m rate25/s; limit_req_status 429; # other configs.. @@ -64,7 +64,7 @@ http { } server { - limit_req zone=mylimit burst=20 nodelay; + limit_req zone=mylimit burst=25 nodelay; # other configs.. diff --git a/v2/thirdpartypasswordless/rate-limits.mdx b/v2/thirdpartypasswordless/rate-limits.mdx index 3b1db5865..e271596da 100644 --- a/v2/thirdpartypasswordless/rate-limits.mdx +++ b/v2/thirdpartypasswordless/rate-limits.mdx @@ -20,7 +20,7 @@ To know more about rps and bursts, please [this nginx document](https://www.ngin ::: ## Free tier -The free tier of the managed service has a rate limit of 10 requests per second with a burst of 20 requests per second (with nodelay). This should be enough for 2 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). +The free tier of the managed service has a rate limit of 25 requests per second with a burst of 25 requests per second (with nodelay). This should be enough for 5 concurrent sign in / up (each sign in API call queries the SuperTokens core multiple times). :::important Our backend SDK auto retries if it gets a `429` status code from the core (up to 5 times before throwing an error). @@ -54,7 +54,7 @@ http { default $binary_remote_addr; } - limit_req_zone $limit_req_zone_key zone=mylimit:10m rate=10r/s; + limit_req_zone $limit_req_zone_key zone=mylimit:10m rate25/s; limit_req_status 429; # other configs.. @@ -64,7 +64,7 @@ http { } server { - limit_req zone=mylimit burst=20 nodelay; + limit_req zone=mylimit burst=25 nodelay; # other configs..