Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temp Revert backtesting optimizations #606

Merged
merged 1 commit into from
Nov 1, 2024

Conversation

Al4ise
Copy link
Collaborator

@Al4ise Al4ise commented Nov 1, 2024

Description by Korbit AI

What change is being made?

Temporarily revert backtesting optimizations by restoring previous implementations in backtesting_broker.py, removing caching and data access enhancements, and reinstating older methods of data handling and time computations across several modules.

Why are these changes being made?

These changes revert recent optimizations to address possibly unanticipated issues or behavioral changes introduced by them, ensuring backward compatibility and stability in backtesting operations while further investigations or improvements can be planned.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Copy link
Contributor

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review Summary by Korbit AI

Code Execution Comments

  • Use bisect for efficient binary search when filtering option trading dates, improving performance on large datasets.
Files scanned
File Path Reviewed
lumibot/backtesting/backtesting_broker.py
lumibot/entities/data.py
lumibot/entities/dataline.py
lumibot/strategies/strategy_executor.py
lumibot/tools/polygon_helper.py

Explore our documentation to understand the languages and file types we support and the files we ignore.

Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

Korbit Guide: Usage and Customization

Interacting with Korbit

  • You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
  • You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
  • Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
  • Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
  • Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

Customizing Korbit

  • Check out our docs on how you can make Korbit work best for you and your team.
  • Customize Korbit for your organization through the Korbit Console.

Current Korbit Configuration

General Settings
Setting Value
Review Schedule Automatic excluding drafts
Max Issue Count 10
Automatic PR Descriptions
Issue Categories
Category Enabled
Naming
Database Operations
Documentation
Logging
Error Handling
Systems and Environment
Objects and Data Structures
Readability and Maintainability
Asynchronous Processing
Design Patterns
Third-Party Libraries
Performance
Security
Functionality

Feedback and Support

Comment on lines 402 to +403
if asset.asset_type == "option":
# Find the index where asset.expiration would be inserted to keep trading_dates sorted
index = bisect.bisect_right(trading_dates, asset.expiration)
# Slice the list to include only dates up to asset.expiration
trading_dates = trading_dates[:index]
trading_dates = [x for x in trading_dates if x <= asset.expiration]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

category Functionality

Consider using the bisect module for filtering trading dates efficiently.

Tell me more

The current implementation for filtering trading dates for options uses a list comprehension, which can be inefficient for large datasets. Consider using the bisect module to perform a binary search, which would be more efficient. You can find the index where the expiration date would be inserted in the sorted list of trading dates, and then slice the list accordingly. This approach will be faster, especially for large datasets.

Chat with Korbit by mentioning @korbit-ai, and give a 👍 or 👎 to help Korbit improve your reviews.

@grzesir grzesir merged commit 95b2aa9 into dev Nov 1, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants