Add eval seed timing logs and devservices mode#115523
Draft
JoshFerge wants to merge 2 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
evalsdevservices mode for seeded local evalsingest-events,post-process-forwarder-errors, and dedicated taskworkers forrelay,ingest.errors,ingest.errors.postprocess, andissuesseer_eval_seed.*timing logs for eval project ingest, save, post-process/code-mapping enqueue, polling endpoints, auto source-code config, and Relay project-config buildseval-*projects where the code path has project contextWhy
This is a draft/debug PR for the local seeded Seer eval bottleneck. The logs showed
ingest-eventsconsuming the 50 events within a few seconds, whilesentry.tasks.store.save_eventcould start roughly 63s later becauseingest.errorswork was competing withissuestasks on the catch-all taskworker.The new
evalsmode moves the queue topology into Sentry instead of requiring Seer to run manual taskworker commands. It avoids the broadingestmode’s extra transactions/attachments workers and avoids a generic catch-all taskworker for the eval path.Verification
git diff --check.venv/bin/prek run -q check-yaml --files devservices/config.ymlevalsmode and supervisor dependency types3.2-3.8sin the slow runsave_eventsince_received_secondsaround63sin the slow run11.93s, then18.72s