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.

Sign up for GitHub

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

Jump to bottom

Add parallelism for name resolution #3

Open
onetwopunch opened this issue Apr 24, 2021 · 2 comments
Open

Add parallelism for name resolution #3

onetwopunch opened this issue Apr 24, 2021 · 2 comments

Comments

@onetwopunch
Copy link
Owner

Just as it sounds, use multi-threading and have one project ancestry API call per thread. This also means adding locking to the cache.
@onetwopunch
Copy link
Owner Author

No longer necessary with CAI.

@onetwopunch
Copy link
Owner Author

However, it may be a good idea for resolving project, folder and org names...thinking we could have a queue of "ancestor" trees that all need to be resolved and run them all in parallel. The cache would need to have a lock on in though...not sure how much performance this would give us...possibly worth investigating though.

@onetwopunch onetwopunch reopened this Apr 27, 2021
@onetwopunch onetwopunch changed the title Add parallelism for ancestry Add parallelism for name resolution Apr 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@onetwopunch