Reporting many warnings is expensive
Customer has a workflow with a large number of hints that come from another workflow system that produce "unrecognized hint" on Arvados. These get reported to the API server. This gets slow because it is an API interaction each time, and the update operation is returning the entire container record which contains the entire workflow contents.
Updated by Peter Amstutz about 1 month ago
19413-warning-update @ 7f510760c01e6a0c4509d29dc5966ee5a2129f22
- There was already a limit imposed on how many warnings to show, the problem is that it would continue uselessly updating the runtime status, even though it was not making any changes to the text
- New behavior, if the text won't change, don't update the record
- Tested on customer workflow, confirmed it reduces workflow startup on the order of 10-15 minutes!