β‘ Bolt: Optimize CLI output string allocations #496
Merged
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.
π‘ What: Optimized
TaskStatus::colored_stringto return cached&'static strusingonce_cell::sync::Lazyand refactoredformat_durationto avoid intermediateStringallocations.π― Why:
TaskStatus::colored_stringwas allocating a newString(with ANSI codes) for every single task execution. In a playbook with many tasks/hosts, this adds up.format_durationwas using multipleformat!calls and slice manipulations that allocated temporary strings.π Impact:
TaskStatus::colored_stringis now zero-allocation after first use.π¬ Measurement:
cargo test --bin rustible output::tests.once_cellis an existing dependency.TaskStatussignature change is safe as it is internal to the binary crate's CLI module.PR created automatically by Jules for task 3146391609273665638 started by @dolagoartur