Parallel time-range sync for 4-5x speedup#12
Open
kittleik wants to merge 1 commit intowarproxxx:mainfrom
Open
Conversation
- Splits time range into N segments, syncs in parallel with ThreadPoolExecutor - Sticky cursor optimization: skips follow-up batches when boundary count < threshold - Graceful shutdown on SIGINT/SIGTERM, per-worker logging - Tested: 2 workers, 36k records in 28.6s (1273 rec/s)
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.
What
New
parallel_sync.pyscript that splits the sync time range into N segments and syncs them in parallel using ThreadPoolExecutor.Key features
parallel_logs/worker_N.logTest results
Usage
pkill -f update_goldsky.py # stop current sync first python3 parallel_sync.py --workers 5