History

Raise free-tier execution rate limit to 10k/hour (#1931)

Rhys Sullivan committed 2 months ago

Commit 9cdf4fe1 parent caa03912 files · +2 −2Browse files

Unified · Split

2 files
  1. apps/cloud/src/engine/execution-rate-limit.ts +1 −1
  2. e2e/setup/execution-limits.ts +1 −1
apps/cloud/src/engine/execution-rate-limit.ts+1−1
@@ -47,7 +47,7 @@ export const RATE_LIMIT_WINDOW_MS = 3_600_000; · 46 unmodified lines
47// against the largest customer is a losing game, so the number no longer tries47// against the largest customer is a losing game, so the number no longer tries
48// to describe them — paid orgs are exempt below, and this now has only48// to describe them — paid orgs are exempt below, and this now has only
49// free-tier abuse to cover, which is what it was picked for.49// free-tier abuse to cover, which is what it was picked for.
50export const EXECUTIONS_PER_ORG_PER_HOUR = 1000;50export const EXECUTIONS_PER_ORG_PER_HOUR = 10_000;
51// Counter DO slower than this => fail open rather than stall executions.51// Counter DO slower than this => fail open rather than stall executions.
52const RATE_LIMIT_CHECK_TIMEOUT_MS = 2_000;52const RATE_LIMIT_CHECK_TIMEOUT_MS = 2_000;
53// Exemption lookup slower than this => treat as unresolved.53// Exemption lookup slower than this => treat as unresolved.
e2e/setup/execution-limits.ts+1−1
@@ -5,7 +5,7 @@ · 4 unmodified lines
5//5//
6// Picking the value is a squeeze from both sides. It must be LOW enough that6// Picking the value is a squeeze from both sides. It must be LOW enough that
7// the backstop scenario can exhaust it with real sequential executions (prod's7// the backstop scenario can exhaust it with real sequential executions (prod's
8// 1000/hour cannot be reached in a test), and HIGH enough that no other8// 10,000/hour cannot be reached in a test), and HIGH enough that no other
9// scenario trips it: the counter is per organization and every `execute` a9// scenario trips it: the counter is per organization and every `execute` a
10// scenario runs counts against its org, so this must exceed the busiest10// scenario runs counts against its org, so this must exceed the busiest
11// single-org scenario's execute count (currently toolkits-mcp at ~8) with11// single-org scenario's execute count (currently toolkits-mcp at ~8) with