⚡ Optimize redundant string allocation in header capture checks #77
Conversation
- Add fast-path for lowercase headers using Cow and char check - Refactor repetitive logic into `to_lowercase_cow` helper - Improve performance of `should_capture_header`, `should_capture_response_header`, and `is_sensitive_header` - Benchmark showed ~32% improvement for lowercase headers (common case) Co-authored-by: Tuntii <121901995+Tuntii@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. |
💡 What: Optimized
InsightConfig::should_capture_headerand related methods to avoid memory allocation when the input string is already lowercase.🎯 Why: Previously, every call to these methods allocated a new
Stringviato_lowercase(), even if the header name was already lowercase (which is standard for HTTP/2). This created unnecessary GC pressure (in a managed language context) or heap churn in Rust.📊 Measured Improvement: Benchmarking showed a reduction in execution time from ~472ms to ~359ms (~1.3x faster) for 5 million iterations on lowercase inputs, with negligible overhead for mixed-case inputs. This translates to reduced CPU usage and memory allocator traffic in high-throughput scenarios.
PR created automatically by Jules for task 18012793317040302205 started by @Tuntii