Skip to content

⚡ Optimize vector usage in Multiplicator setup#369

Open
tlepoint wants to merge 1 commit intomainfrom
optimize-multiplicator-vector-1448834772391169533
Open

⚡ Optimize vector usage in Multiplicator setup#369
tlepoint wants to merge 1 commit intomainfrom
optimize-multiplicator-vector-1448834772391169533

Conversation

@tlepoint
Copy link
Owner

@tlepoint tlepoint commented Feb 4, 2026

💡 What:
Replaced extended_basis.append(&mut ctx.moduli().to_vec()); with extended_basis.extend_from_slice(ctx.moduli()); in crates/fhe/src/bfv/ops/mul.rs.

🎯 Why:
To avoid allocating a temporary Vec when appending a slice to a Vec. extend_from_slice copies elements directly.

📊 Measured Improvement:
Measured using a custom criterion benchmark Multiplicator::default.

  • Baseline: 17.04 ms
  • Optimized: 17.43 ms
  • Result: No statistically significant difference (within noise). The operation is dominated by prime generation and other setup steps. However, the change is a best-practice optimization that removes an unnecessary allocation.

PR created automatically by Jules for task 1448834772391169533 started by @tlepoint

Replaced `vec.append(&mut slice.to_vec())` with `vec.extend_from_slice(slice)` in `crates/fhe/src/bfv/ops/mul.rs`.
This avoids allocating a temporary vector for the slice content before moving it to the destination vector.

Measured performance impact:
- Baseline: ~17.04 ms
- Optimized: ~17.43 ms
- Difference is within noise threshold, but the change avoids unnecessary allocation.

Co-authored-by: tlepoint <1345502+tlepoint@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