Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Substitutes
sim_swapforpure_swap, or at least, does an analysis on its benefits and cons. Thesim_swapapproaches executes a swap and then reverts whilepure_swapallows this without reverting back those writes. Initially I thought this writes were actually commited to DB but I realized this is not the case while benchmarking:sim_swapsimply maintains in-memory vars that later are discarded.All in all I think having a
pure_swapapproach perhaps is more readable and I saw a 38us optimization while benchmarking, probably due to the overhead of having to dowith_transaction+rollbackin the sim_swap case. But this optimization is negligible if we take into account db reads and writes, which clearly domintate. Additionally, it is also true thispure_swapposes an additional maintainability layer.At least I want to propose this PR so that the team is aware of my findings. I generated a ton of tests to make sure both yield the same results
Related Issue(s)
Type of Change
Breaking Change
If this PR introduces a breaking change, please provide a detailed description of the impact and the migration path for existing applications.
Checklist
./scripts/fix_rust.shto ensure my code is formatted and linted correctlyScreenshots (if applicable)
Please include any relevant screenshots or GIFs that demonstrate the changes made.
Additional Notes
Please provide any additional information or context that may be helpful for reviewers.