Skip to content

Conversation

shellmayr
Copy link
Member

  • Use 80 instead of 100 orgs, and 4000 projects intead of 5000 projects per query
  • Intent is to reduce the size of the query, so snuba does not run into query timeouts as frequently when running these queries
    Closes TET-1224

@shellmayr shellmayr requested a review from a team as a code owner October 10, 2025 11:18
Copy link

linear bot commented Oct 10, 2025

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Oct 10, 2025
Copy link
Member

@vgrozdanic vgrozdanic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You think that 20% reduction will be enough?

Do we want to go more aggressive and do a binary search? E.g. start with half and take it from there up or down

@shellmayr
Copy link
Member Author

@vgrozdanic I get the idea, and I somewhat agree that we should do this if this were in a vacuum, but I want to be careful w.r.t. the cycles of the tasks. Each of these queries adds some time to the outer loop, so we should be careful not to disrupt the rhythms too strongly

@shellmayr shellmayr merged commit 89ee6e7 into master Oct 13, 2025
95 of 97 checks passed
@shellmayr shellmayr deleted the shellmayr/chore/run-dynamic-sampling-on-smaller-query-sets branch October 13, 2025 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants