-
Notifications
You must be signed in to change notification settings - Fork 48
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
Ideas for improve loading times #38
Labels
Comments
Thank you! I'm away at the minute but will test this on a new version once I'm back 👍🏼👍🏼👍🏼 |
nbrown02
added
enhancement
New feature or request
question
Further information is requested
labels
Aug 27, 2021
Closing as suggestion would mean solution would be incompatible with users on the 'Agile' process template |
Let me have a look and get back to you (reopening) |
Ah ok - looks like I've got it working now 👍 |
Fixed in the latest version - thank you again :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
The slowest loading tables seem to be "WorkItems Bl0cked" and "WorkItems Daily Bl0cked Count". I believe this is related to the sheer amount of data that has to be acted on when transformations are done directly to the WorkItemRevisions endpoint. Specifically this is happening due to the "Removed Columns" action right after the OData feed. This action is just selecting the only 6 columns needed in both tables because the WorkItemRevisions endpoint returns a lot of more columns (aka more data). This is not needed since the endpoint accepts a column selection parameter.
Solution
In both tables instead of querying the endpoint with a filter, do it with a select and a filter and then remove the subsequent Removed Columns (select columns) action.
Instead of:
Do:
This removes the need for a subsequent select action in the BI side.
I've tested this approach and it cuts loading time for those tables in about 75%
The text was updated successfully, but these errors were encountered: