⚡ Bolt: optimize synthetic vector generation#223
Conversation
Replaced `crypto.createHash` with Node 22's one-shot `crypto.hash` and replaced `toFixed(8)` with faster numeric rounding in `syntheticVector`. Measurable impact: - Reduced latency from ~8.6ms to ~4.8ms per vector (~44% reduction). - Reduced string allocations in hot loops. - Maintained deterministic output. Co-authored-by: hackerxj2010 <198651211+hackerxj2010@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 the
syntheticVectorgeneration path in@jeanbot/ai.crypto.createHash().update().digest()to the moderncrypto.hash()one-shot API.Number(val.toFixed(8))with efficient numeric rounding:Math.round(val * 1e8) / 1e8.normalizeTextcalls in the generation loop.🎯 Why: Synthetic vector generation (1536 dimensions) involves thousands of hashing and formatting operations. Profiling showed that
createHashobject overhead andtoFixedstring allocations were significant bottlenecks.📊 Impact:
🔬 Measurement: Verified using a benchmark script executing
generateEmbeddingswithforceSynthetic: truefor 100 iterations on Node v22.22.1. All integration and unit tests passed.PR created automatically by Jules for task 2717732916546907115 started by @hackerxj2010