Skip to content

SL-1950: Increase geo backfill batch size and frequency - #74537

Merged
artem-vavilov merged 1 commit into
stagingfrom
SL-1950/project-storage-geo-backfilling
Aug 11, 2026
Merged

SL-1950: Increase geo backfill batch size and frequency#74537
artem-vavilov merged 1 commit into
stagingfrom
SL-1950/project-storage-geo-backfilling

Conversation

@artem-vavilov

@artem-vavilov artem-vavilov commented Aug 11, 2026

Copy link
Copy Markdown
Member

Increases the geo backfill batch size from 100,000 to 150,000 records and changes the schedule from every 15 minutes to every 10 minutes.

Based on the first day's logs, jobs processing 100,000 records are consistently completing in about 5–6 minutes, which gives us enough headroom to increase both the batch size and frequency.

With the 10-hour daily backfill window, this increases throughput from about 4 million to 9 million records per day, reducing the estimated time to backfill all 90 million records from roughly 23 days to about 10 days.

Links

@artem-vavilov
artem-vavilov requested a review from a team as a code owner August 11, 2026 17:03

@carl-codeorg carl-codeorg left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

:shipit:

# Backfills geolocation data for anonymous project storages every 15 minutes from 02:00 to 11:45 UTC.
cronjob at: '*/15 2-11 * * *', do: "#{deploy_dir('bin', 'cron', 'perform_job')} ProjectStorage::AnonymousGeoBackfillingJob '{\"limit\": 100000}'"
# Backfills geolocation data for anonymous project storages in batches of 150k every 10 minutes from 02:00 to 11:50 UTC.
cronjob at: '*/10 2-11 * * *', do: "#{deploy_dir('bin', 'cron', 'perform_job')} ProjectStorage::AnonymousGeoBackfillingJob '{\"limit\": 150000}'"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is it worth making the batch size a DCDO setting?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I thought about this too, but I do not think we need it yet. If we start seeing significant spikes and need to adjust the batch size frequently, it would make sense to move it to DCDO. Since the backfill has been relatively smooth so far, I would prefer to keep these changes tracked through the code history and PRs

@artem-vavilov
artem-vavilov merged commit e358543 into staging Aug 11, 2026
8 checks passed
@artem-vavilov
artem-vavilov deleted the SL-1950/project-storage-geo-backfilling branch August 11, 2026 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants