Use multithreading for GraphQL workflow ingestion #19
Conversation
This file contains 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.
This PR is the first step in resolving #11. I've moved both the organization repo list query and GraphQL workflow query functionality into the Ingest class. The speed increase is quite impressive. At this point the biggest limiting factor is GitHub's secondary rate limits. Since this is an IO-bound operation it's good to start with multi-threading because the GIL is not going to be the limiting factor.
gato-x e -t microsoft -sr: Enumeration of 4829 repositories with run log analysis off.Sun Sep 15 01:07:00 EDT 2024Sun Sep 15 01:09:47 EDT 2024This used to take over 10 minutes.