-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Lazily gather the lists of available sls data from the master #54468
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
Conversation
Note : I have tested a similar patch for pillars (in |
3a2d096
to
581a810
Compare
@twangboy Could you please review? |
@dwoz I've added tests |
b571779
to
332de26
Compare
@thatch45 can you take a look at this? It looks pretty straightforward to me but I'm not 100% familiar with the implications of futzing with the states. |
I really like this approach, it is clean, and it can be pulled out if there are issues. But this does look like it should work. |
@twangboy your turn! |
@sathieu could you please resolve merge conflicts? |
@sathieu could you please resolve the merge conflicts and run the pre-commit script on your code to re-format it with
next time you'll commit it will be ran automatically. |
@DmitryKuzmenko I've rebased and used pre-commit hook. I had to use Then, it failed with:
I've commited again (black and isort already runt) with |
This improves significantly the performance of a state.apply when using GitFS and a lot of branches.
@sathieu thank you for report. We'll work on it. |
@sathieu did you use If just installing pre-commit that way doesn't work running |
@waynew ah, it looks it's my fault. I should recommend |
What does this PR do?
This improves significantly the performance of a state.apply when using
GitFS and a lot of branches.
What issues does this PR fix or reference?
none
Previous Behavior
3 minutes with 276 branches.
New Behavior
25 seconds
Tests written?
No. Already covered by existing tests.
Commits signed with GPG?
No