fix members of a multibar always rendering #630
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
I noticed a rather inconvenient performance issue with
MultiBar
, contrary to regular progress bar no rate limiter will prevent computing the string that will displayed for a given memberProgressBar
. The cost of this "hidden rendering" can quickly add up if unicode+ANSI decoding features are enabled.My implementation relies on actually rejecting calls to
DrawTarget::drawable
for multi-bar targets but marking the member as "delayed" for later redraw. When a call for drawable is actually accepted, all delayed member or first redrawn.Here is an example flamegraph from the application I'm building, using the main branch :
A recurring call to
set_length
takes 30% of the running time in the example above. With my patch it is down to <4% :