Skip to content

⚡ Bolt: Avoid redundant clone in media cache insert#764

Open
kevinaboos wants to merge 1 commit intomainfrom
bolt-optimize-media-cache-clone-12072460591131631633
Open

⚡ Bolt: Avoid redundant clone in media cache insert#764
kevinaboos wants to merge 1 commit intomainfrom
bolt-optimize-media-cache-clone-12072460591131631633

Conversation

@kevinaboos
Copy link
Member

💡 What: Removed an unnecessary .clone() call on MediaRequestParameters in src/media_cache.rs.
🎯 Why: MediaRequestParameters contains OwnedMxcUri (a string wrapper) and other data. Cloning it is an unnecessary allocation because the original variable request is not used afterwards in the insert_into_cache function.
📊 Impact: Reduces memory allocations and CPU cycles for every media fetch operation (images, avatars, etc.). While micro-optimization, it affects a frequent path in media-heavy rooms.
🔬 Measurement: Verified via cargo check that ownership rules are satisfied. No regression in logic as request was implicitly dropped immediately after the clone previously.


PR created automatically by Jules for task 12072460591131631633 started by @kevinaboos

…ters

Removes a redundant `clone()` of `MediaRequestParameters` in `insert_into_cache`.
The `request` variable is owned by the function and not used after the point where it was cloned, so it can be moved instead.
This avoids potentially expensive string allocations (e.g. for the MXC URI) on every media fetch.

Co-authored-by: kevinaboos <1139460+kevinaboos@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant