High volume on TimeSales freezes/RAM requirements

[mikev777]

What are the recommended RAM requirements for the Desktop API if using real time Time Sales data?

I am charting the S&P 500 e-mini futures and whenever i get a large volume of data, both my application and eSignal freeze up.

Is it due to the machine's inability to handle all the events coming in or could it be the way I'm displaying the TS data (I'm sending a windows message to a microsoft rich edit control) which may be resource-consuming?

I have a little over 700 Mbytes RAM in my machine.

What are the recommended memory requirements and what is the best way to handle the display of TimeSales data?

Thanks,
Michael

[GenSpoo]

That is enough RAM, unless you have a lot of other things running. CPU speed is an issue as well. But in general if all you are watching is the ES and the system is freezing, it is possibly due to how you are retrieving the data. Maybe if we could see your OnTimeSalesChanged function, we might see an efficiency issue. Are you grabbing just the new ticks as they come in, or are you calling GetTimeSalesBar on every tick every time?

Cheers... George

[mikev777]

OK. I'll post the code OnTimeSalesChanged function this weekend.

However, I am calling GetTimeSalesBar only on the new ticks, as I keep a counter of how many ticks there have been (as per example code).

Somebody told me ES has A LOT of volume and the computer can freeze up. Even if I'm not running my application, eSignal does freeze up occasionally for a second or so. With my application, I can be stuck for 10-40 seconds.

Michael

[Guest]

If I were developing with this API for something that trades as much as the eMini's I would have at least 1 GB of RAM. RAMs fairly inexpensive, so I would max out my machine.

[mikev777]

Robi,

Thanks. Actually somebody else has also just told me that for one of the competitor platforms (not to be mentioned) he recommends minimum 2GBytes RAM for e-Minis. That's without using an API.

Thanks. I'll try that. If it doesn't work, I'll come back.

Michael

[Guest]

Please keep me posted.