feat(backtest-optimization): reduce overhead of calls in Orders #472
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.
IMPORTANT: Changes in Live-plugin is required
orders are used a lot, and each filed is an orm field which give an overhead for every setter / getter of the attributes.
refactor it to simple dataclass remove this overhead.
Here is an example of strategy that is always in position and has a lot of entry and exit orders
Current state
With these modification
The numbers are getting bigger when there are more orders for longer times.