⚡️ Speed up function sigmoid_stable by 26%
#570
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📄 26% (0.26x) speedup for
sigmoid_stableincodeflash/process/infer.py⏱️ Runtime :
1.78 milliseconds→1.42 milliseconds(best of298runs)📝 Explanation and details
Here is an optimized version of your
sigmoid_stablefunction. The performance bottleneck is due to repeated calls tonp.exp(x)within thenp.wherefunction, causing unnecessary recomputation over potentially large arrays.We'll precompute
exp_x = np.exp(x)andexp_neg_x = np.exp(-x)outside ofnp.whereto avoid recomputation and improve cache use. This significantly reduces redundant computation for both branches of thenp.where.Explanation of Changes:
exp_neg_xandexp_xout ofnp.whereto avoid duplicate calculations.np.expcalls down to one each, regardless of input.This will make the function significantly faster, especially on large arrays. The output is mathematically identical.
✅ Correctness verification report:
🌀 Generated Regression Tests and Runtime
⏪ Replay Tests and Runtime
To edit these changes
git checkout codeflash/optimize-sigmoid_stable-mdf1ifk6and push.