You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current iteration of harvest, it can take several days to run harvest on a large bundle. I think it would be a simple addition to the application. The inclusion of the feature could help easily gauge if performance is better or worse with new releases of harvest and registry configuration, as well as other local system resource contention.
π Additional Details
Add execution time to harvest summary
Acceptance Criteria
Given a data set When I perform harvest run Then I expect the final output summary to contain "Execution Time: XXXs"
βοΈ Engineering Details
No response
π I&T
No response
The text was updated successfully, but these errors were encountered:
jordanpadams
changed the title
As a data loader, I want to have an quick reference on how long the harvest job ran. Please add the amount of time the run took as part of the execution summary/
As a data loader, I want to know how long it took for a harvest job run
Dec 18, 2024
@scholes-ds I'm sure you already know this, and I know this is not ideal, but updating your procedures to do something like this everytime you execute Harvest may help:
Checked for duplicates
Yes - I've already checked
π§βπ¬ User Persona(s)
Node operator
πͺ Motivation
With the current iteration of harvest, it can take several days to run harvest on a large bundle. I think it would be a simple addition to the application. The inclusion of the feature could help easily gauge if performance is better or worse with new releases of harvest and registry configuration, as well as other local system resource contention.
π Additional Details
Acceptance Criteria
Given a data set
When I perform harvest run
Then I expect the final output summary to contain "Execution Time: XXXs"
βοΈ Engineering Details
No response
π I&T
No response
The text was updated successfully, but these errors were encountered: