Increase historical ohlcv backfilling speed AND Fix incorrect ohlcv during live fetching #46
Conversation
This file contains 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
1. Increase historical ohlcv backfilling speed 2. Fix incorrect ohlcv during live fetching
1. Increase historical ohlcv backfilling speed 2. Fix incorrect ohlcv during live fetching
qinwang-ai
reviewed
Aug 30, 2021
There was a problem hiding this comment.
The option 'ohlcv_limit' can be defined at store.getdata(ohlcv_limit=1000). Although arbitrarily set 1000 in default is useful which can accelerate the backfilling period at the beginning. However, it is too waste in latter live fetching period since it will cause too many responses.
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.
No description provided.