Skip to content

chore(hybridcloud) Use a more efficient RPC call in ratelimiting - #76258

Merged
markstory merged 1 commit into
masterfrom
chore-ratelimit-rpc
Aug 15, 2024
Merged

markstory merged 1 commit into
masterfrom
chore-ratelimit-rpc

Conversation

@markstory

Copy link
Copy Markdown
Member

Fetching an installation + sentryapp + apiapplication only to use the organization_id contributes to higher latency. If we use a tailor made RPC call we should have better response times as there are fewer queries and less data transferred.

Fetching an installation + sentryapp + apiapplication only to use the
organization_id contributes to higher latency. If we use a tailor made
RPC call we should have better response times as there are fewer queries
and less data transferred.
@markstory
markstory requested a review from a team August 15, 2024 15:08
@markstory
markstory requested a review from a team as a code owner August 15, 2024 15:08
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Aug 15, 2024
@markstory
markstory merged commit 4fb67fb into master Aug 15, 2024
@markstory
markstory deleted the chore-ratelimit-rpc branch August 15, 2024 18:26
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 31, 2024

This branch was successfully deployed

1 active deployment
Preview — fc33b16f Deployed Aug 15, 2024 by vercel[bot]
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants