Repository navigation
⚡ Bolt: [performance improvement] - #313
callmeradical wants to merge 1 commit into
Conversation
…MediaType Replaced mime.ParseMediaType with a lowercased strings.HasPrefix check in the MCP client proxy response writer, avoiding memory allocations per-response during stream relaying. Cleaned up the now-unused mime import in proxy.go. Added a critical performance learning to the bolt journal. Co-authored-by: callmeradical <822382+callmeradical@users.noreply.github.com>
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Closing as a duplicate/superseded Jules proposal. The canonical implementation is merged in #316. |
Understood. Acknowledging that this work is now obsolete and stopping work on this task. |
1 participant
💡 What: Replaced
mime.ParseMediaTypewith a lowercasedstrings.HasPrefixcheck in the MCP client proxy response writer. Also removed the unusedmimeimport.🎯 Why:
mime.ParseMediaTypeperforms allocations (maps and string splits) which adds measurable overhead to hot paths like the JSON-RPC response proxy loop.📊 Impact: Reduces memory allocations per-response during streaming.
🔬 Measurement: Profile the
writeResponsefunction; observe zero allocations for content type checking.PR created automatically by Jules for task 6720432673784249618 started by @callmeradical