Hello,
I have 2 WL installations. One with build 88 and one with build 89. In build 89 I noticed that as soon as the provider Next Earnings Date is activated, every backtest, no matter if the indicator Next Earings is used in the strategy or not, becomes extremely slow. What used to take a few minutes now takes hours. As soon as I deactivate the provider, the speed returns to normal.
This is not the case in Build 88. Same strategies and same datasets.
I hope I have observed this correctly and described it clearly.
Thanks
I have 2 WL installations. One with build 88 and one with build 89. In build 89 I noticed that as soon as the provider Next Earnings Date is activated, every backtest, no matter if the indicator Next Earings is used in the strategy or not, becomes extremely slow. What used to take a few minutes now takes hours. As soon as I deactivate the provider, the speed returns to normal.
This is not the case in Build 88. Same strategies and same datasets.
I hope I have observed this correctly and described it clearly.
Thanks
Rename
Hello,
You should update the Fundamental extension to B13:
* Fix: NextEarningsDate event provider (stopped returning dates due to backend changes).
https://www.wealth-lab.com/extension/detail/Fundamental#changeLog
You should update the Fundamental extension to B13:
* Fix: NextEarningsDate event provider (stopped returning dates due to backend changes).
https://www.wealth-lab.com/extension/detail/Fundamental#changeLog
Thank you for the feedback. The provider was already up to date when I noticed the problem.
In the last build, I replaced a couple of dead endpoints with actual ones. Perhaps you're having some network connectivity issue with one of the resources the provider hits. It happens. There's no guarantee that it works fast - and that it even works.
Do you have an Earnings provider checked off? You need one to make the NextEarning Date provider work effectively. I use Zacks as my Earnings provider, which is fast.
Hello,
I do not believe that this is a network problem.
Here is an example to illustrate where the problem is:
I have a simple example strategy without an earnings indicator:
- All strategy windows are closed
- I open the Data Manager and deactivate the Next Earnings Date Provider and close the Data Manager again.
- I open the example strategy and start the backtest
- The run takes a few seconds
- I close the strategy window
- I open the Data Manager and activate the Next Earnings Date Provider and close the Data Manager again
- Now I open my example strategy again and start the backtest
- Loading the data of the first symbol (here GE) takes several minutes
Is this normal? In Build 88, the backtest of the same strategy is equally fast in both cases and runs through in a few seconds. Why is this different between Build 88 and 89?
I do not believe that this is a network problem.
Here is an example to illustrate where the problem is:
I have a simple example strategy without an earnings indicator:
- All strategy windows are closed
- I open the Data Manager and deactivate the Next Earnings Date Provider and close the Data Manager again.
- I open the example strategy and start the backtest
- The run takes a few seconds
- I close the strategy window
- I open the Data Manager and activate the Next Earnings Date Provider and close the Data Manager again
- Now I open my example strategy again and start the backtest
- Loading the data of the first symbol (here GE) takes several minutes
Is this normal? In Build 88, the backtest of the same strategy is equally fast in both cases and runs through in a few seconds. Why is this different between Build 88 and 89?
I cannot reproduce what you're showing as the NextEarningsDate event provider updates its data quickly for me.
Certainly not normal, I can't reproduce either!
While researching the problem further, I noticed this error message:
For some reason specific to your computer (like firewall setup or whatever) and not reproducible on our machines, the provider fails to get requested data even trying a fallback route.
Your Response
Post
Edit Post
Login is required