-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-6163] Speed up list items command - Only call GetGlobals() when we actually need them #7855
Conversation
Thank you for your contribution! We've added this to our internal Community PR board for review. |
Fixed Issues
|
Since we only need it as a backup if accountVaultTimeoutAction is null/undefined, there should be no need to call this function every time. While the overhead may seem trivial at first glance, it can add up to a massive increase in runtime when the function is called repeatedly in quick succession (e.g. when running `bw list items` where it is executed once for every item). In my concrete case this change leads to a 20x speedup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @watzkuh, thanks for your PR! The change looks good, and I've tested and experienced the bw list items
time go from 190 seconds to 4 seconds, I'm going to send this PR to QA for some final testing, as soon as it's done I'll merge this.
This has gone through QA and is ready to merge, thanks for your contribution! |
Is this landed yet? I tested it with a prerelease artifact from 2024.5.0 and am still seeing extremely long |
Pretty slow for me too. I notice that i hangs a little bit after it prints out the results, so it's not getting the actual items that are slow. I feel like this is slow as well: |
Type of change
Objective
Speed up the CLI list items command (see issue #7742)
Code changes
Since we only need it as a backup if
accountVaultTimeoutAction
is null/undefined, there should be no need to call this function every time.While the overhead may seem trivial at first glance, it can add up to a massive increase in runtime when the function is called repeatedly in quick succession (e.g. when running
bw list items
where it is executed once for every item).In my concrete case this change leads to a 25x speedup.
Before:
After: