Why don't you save the data on the local machine so only the new candles will be downloaded? with the option of refreshing the chart from server, witch will download everything?
If you have 20 charts.. it takes a lot of time.
Just a thought
Save data
-
Stanley Miller
- Posts: 556
- Joined: 26 Jul 2005
- Has thanked: 3 times
Actually there is no reason to save data locally. The advanced technology we use provides high data compression, this keeps the data packets small, which means you should receive the data at remarkably fast speed, even on a standard 56k connection. Of course, you can also take full advantage of your DSL or cable modem connection. In practice it takes a few seconds to display a minute chart for almost 5 years, charts with a lesser data volume are displayed instantly.
What data do you have on your charts?
What data do you have on your charts?
I'd have to agree with Dof. Storing data locally would have several advantages. First, I too have really, really slow load times even with only 3 workspaces. (I PMed Alex the workspaces last week). I have a 512/128 ADSL and it takes sometimes 10 minutes to load everything up. Second, I commute to work every day and I like to analyse my charts and do back testing on the train. If the data were stored locally I'd be able to do that, where currently I can not.
I appreciate what you say below but in reality that is not the experience. Opening a single chart once everything is already up and running may only take a little while as you state but to get to that point is a painfully slow experience.
I appreciate what you say below but in reality that is not the experience. Opening a single chart once everything is already up and running may only take a little while as you state but to get to that point is a painfully slow experience.
-
Alex Kramer
- Posts: 834
- Joined: 23 Feb 2006
We are analyzing your workspaces and they really seem to be loading slow, which led us to discovering some problems on our server, so we're fixing them presently.
If everything was working fine, with your connection speed it would take about 10 seconds to download, so this is why we like many other charting product developers, are not implementing local storage. Implementing it would only complicate the product if data downloading works well.
Going to the train commute you can just set the notebook to hibernate - data won't update but you'll see the opened charts.
If everything was working fine, with your connection speed it would take about 10 seconds to download, so this is why we like many other charting product developers, are not implementing local storage. Implementing it would only complicate the product if data downloading works well.
Going to the train commute you can just set the notebook to hibernate - data won't update but you'll see the opened charts.
I bet you have a good algorithm for compressing, but one thing I've notice. There is a big difference between loading time on saturday and and monday. THe idea is that when there is no activity the charts are loading how you expect, but when things get crowded...
So maybe, and I say maybe, you're not doing the testing in real life scenario.
So maybe, and I say maybe, you're not doing the testing in real life scenario.
-
Alex Kramer
- Posts: 834
- Joined: 23 Feb 2006
Alex,
Under what conditions are you getting 10 sec chart loads? I can honestly say that I can never get anywhere near that sort of performance. Even just 12 months of 4hr data (less than 3000 bars) takes considerably longer than that.
I still think that storing the data locally would be a much better proposition (MT4 and TS both do)
Under what conditions are you getting 10 sec chart loads? I can honestly say that I can never get anywhere near that sort of performance. Even just 12 months of 4hr data (less than 3000 bars) takes considerably longer than that.
I still think that storing the data locally would be a much better proposition (MT4 and TS both do)
