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.
We had three 100% cpu spikes before, all were due to nested operations, with 9e99999999 at the base.
After some investigation, I found the root cause to be the cloning of the top exponent number every op.
After I changed that to move, the example I used to test went down to ~1s total time.
As that is still slow, I changed the integer construction limit to 10000000 (one order of magnitude less, switches to approximate earlier).
The latest hours long problem was due to the copying of that top exponent thousands of times. I limited the steps to 10 for now.