Now the problem is that WL8 is abysmally slow. One keystroke or even cursor movement will send a "Not Responding" message. Can't trade that way.
I'll be hanging on to (and trading with) with WL7 until these bugs are resolved. WL7 is a rocket compared to WL8
I thought that maybe the some of the other Historical Providers I installed originally may be slowing me down. Is that possible? If so, how do I remove those, pls?
I'll be hanging on to (and trading with) with WL7 until these bugs are resolved. WL7 is a rocket compared to WL8
I thought that maybe the some of the other Historical Providers I installed originally may be slowing me down. Is that possible? If so, how do I remove those, pls?
Rename
After update of what: to a new build? a historical/event data update? We don't have a radar to see what's happening on the user's end. Be clear and detailed please, otherwise there is no way to understand an issue.
I realize you don't have radar, Eugene.
Let me be more clear.
When I logged on this AM I was instructed to update the build on WL8, which I did.
This resulted in very slow operation, producing "not responding" messages, occasionally requiring reboots to reset the program that becomes completely unresponsive.
However, alternatively, WL7 remains steady and stable, and fast.
Let me be more clear.
When I logged on this AM I was instructed to update the build on WL8, which I did.
This resulted in very slow operation, producing "not responding" messages, occasionally requiring reboots to reset the program that becomes completely unresponsive.
However, alternatively, WL7 remains steady and stable, and fast.
Or maybe we can schedule a zoom call to see the issue first hand? It might be easier to figure out what’s going on with these reports of such sluggishness in WL8 that we can’t duplicate locally.
1. Data Manager
- Uncheck the Historical Providers you don't use
- Uncheck the Event Providers that are not required
2. Intraday Data
Especially if you use IB for intraday data, make sure that the charts initialize to a reasonable range - like 3000 bars or less. Preferences (F12) > Data > Amount of Data to Load into Chart.
- Uncheck the Historical Providers you don't use
- Uncheck the Event Providers that are not required
2. Intraday Data
Especially if you use IB for intraday data, make sure that the charts initialize to a reasonable range - like 3000 bars or less. Preferences (F12) > Data > Amount of Data to Load into Chart.
Done, but no improvement
Write zoom@wealth-lab.com and let's set up a zoom meeting like Glitch suggested. Send us a range of times you're available. Best during market hours.
OK it's not what you're doing in WL8 after update - maybe some background thread/task in WL8 got stuck for its own reason. Do you notice high CPU utilization by the WealthLab8.exe process in Task Manager?
No, I do not.
Actually WL8 is about the same as WL7
Very small CPU numbers
Actually WL8 is about the same as WL7
Very small CPU numbers
Your Response
Post
Edit Post
Login is required