Skip to content

⚡ Bolt: Optimize backpropagation to use zero-copy ownership transfer#141

Open
teerthsharma wants to merge 1 commit into
masterfrom
bolt-zero-copy-backprop-5293134432065391883
Open

⚡ Bolt: Optimize backpropagation to use zero-copy ownership transfer#141
teerthsharma wants to merge 1 commit into
masterfrom
bolt-zero-copy-backprop-5293134432065391883

Conversation

@teerthsharma

Copy link
Copy Markdown
Owner

💡 What: Replaced .as_ref().unwrap().clone() with .take().unwrap() in DenseLayer::backward for last_z and last_input. Also refactored MLP::forward to borrow and pass the initial input directly to the first layer, eliminating an unnecessary clone.
🎯 Why: Tensor instances in aether-core use Rc<RefCell<Vec<f64>>> for data, but cloning them still requires a heap allocation for shape and strides vectors. During backpropagation, these cached tensors are consumed entirely, so moving them transfers ownership without copying metadata.
📊 Impact: Eliminates multiple redundant metadata heap allocations per forward/backward pass during training loops.
🔬 Measurement: Verify changes in crates/aether-core/src/ml/neural.rs. The code is covered by cargo test -p aether-core --offline -- ml::neural which runs cleanly.


PR created automatically by Jules for task 5293134432065391883 started by @teerthsharma

Modified `DenseLayer::backward` to use `Option::take()` instead of `.clone()` for cached tensors, avoiding heap allocations of metadata during the backward pass.
Modified `MLP::forward` to avoid cloning the input tensor on the first layer.

Co-authored-by: teerthsharma <78080953+teerthsharma@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
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