Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: concurrent resource fetching per provider #1065

Conversation

titanventura
Copy link
Contributor

Problem

Template to fetch resources concurrently using worker pools. Implements concurrency for aws fetcher.
Fixes #1014 partially

Changes Made

  • Added worker pool, make use of the worker pool in AWS

Notes

Perf test needed

Checklist

Reviewers

@Azanul @AvineshTripathi @mlabouardy @jakepage91

@titanventura titanventura changed the title Concurrent resource fetching per provider feat: concurrent resource fetching per provider Oct 10, 2023
@mlabouardy mlabouardy requested a review from Azanul October 10, 2023 08:53
Copy link
Collaborator

@mlabouardy mlabouardy left a comment

Choose a reason for hiding this comment

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

any update on the performance benchmark @Azanul ?

@mlabouardy mlabouardy added the aws label Oct 15, 2023
@mlabouardy mlabouardy added this to the v3.1.2 milestone Oct 15, 2023
@Azanul
Copy link
Collaborator

Azanul commented Oct 15, 2023

Before: f2326e9
Before Profile CPU.pb.gz
Before Profile Space.pb.gz

Screenshot 2023-10-15 at 8 31 26 PM

After: 1d46d1d
After Profile CPU.pb.gz
After Profile Space.pb.gz

Screenshot 2023-10-15 at 9 32 16 PM

Tested on M2 Pro with no CPU limit and 10GB RAM limit

@mlabouardy mlabouardy self-requested a review October 16, 2023 11:24
@mlabouardy mlabouardy merged commit ee52e42 into tailwarden:develop Oct 16, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fetch resources concurrently using goroutines
3 participants