⚡ Bolt: Cache XftDraw in Drw struct #168
Draft
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.
⚡ Bolt Performance Improvement
💡 What:
Cached the
XftDrawcontext within theDrwstruct instead of creating and destroying it on every call todrw_text.🎯 Why:
drw_textis a hot path, called for every window title, tag, and status bar element during every redraw. Repeatedly callingXftDrawCreateandXftDrawDestroyinvolves unnecessary memory allocation and potential X server overhead.📊 Impact:
Reduces overhead in the main rendering loop. While exact micro-benchmarks are difficult without an X11 profiling setup, avoiding repeated allocations in a hot loop is a standard optimization practice in C graphics programming.
🔬 Measurement:
Verified via code inspection and build verification. The logic ensures
XftDrawlifecycle matches thedrawable(pixmap) lifecycle.PR created automatically by Jules for task 13421265876079189192 started by @paperbenni