I've been having a huge problem with Metastock 9...100% CPU usage lock-up in fast market conditions. I've done quite abit of testing on this over the last week or so. This condition occurs almost exclusively in fast market conditions with only heavily traded securities like the ES emini futures contract. The Metastock charts are not heavily loaded down with indicators or experts and this occurs with only 1 chart open. Metastock will prompt a dialog box saying something like "Metastock is unable to keep up with the data flow. Please close any additional applications." No other applications except eSignal's data manager were opened. The amount of data being thrown at Metastock 9 by eSignal in fast market conditions is just too much for the Equis Data Server to handle efficiently. I compared this phenomenon with data received simultaneously from IB's TWS using hyperserver lite to connect TWS to Metastock and experienced no such problems. I attached a tick counter on both data providers and found at times a 10 to 1 difference in the amount of tick data being received at any given moment bet by the Equis Data Server when comparing eSignal and TWS data flow. I tested this on two different platforms and experienced lock-up 100% CPU usage depending on the strength and volume of the market move. These tests occurred on Pentium 4 2.53 ghz 1 gb DDR SDRAM and AMD Athlon 64 3500+ 512K DDR2 SDRAM machines. I'm not sure what can be done to rectify this problem. eSignal records every tick in it's data flow (which IB does not) at a specific price Comments or suggestions? Ringo

rokafella: Your post is right there http://forum.equis.com/viewtopic.php?t=1131 I'm still waiting for your answer ... Ringo: I would check for real time update folder as well Patrick :mrgreen:

Because all the securities in that folder are updating real time, so if you happen to have 50 symbols in that fodler, you have 50 securities that update real time for everysingle tick of data ... Most computer can only handle ahandfull if that even ... Patrick :mrgreen:

hey rokafella..... i gave your orignal post alot of thought.... the suggestions given by patrick were the only thing that came to mind that were metastock specific..... the odd thing about your dilemma was the time frame issue..... often programs will max out at start up then settle down but to max after 30 minutes each time, almost points in a direction other that meta.... running QC with several workbooks open and metastock open with 'csco', 'intc' tick charts running , seldom uses over 75% total cpu on mine.... and thats a total with everything else running also.... the only thing i could think of regarding meta, was to not open those 2 charts.... but open 'csco' and 'intc' in tick time frames and see if it again maxes in 30 minutes..... kinda figured you had tried that so didn't post my thoughts...... still studying on it ......h

Hayseed, Can't delete this message. See next one below. Ringo

I sincerely hope the developers of Metastock at Equis focus some needed attention on developing the "Enable Real Time Bars" function so that it doesn't usurp such a significant amount of CPU resources. It is ridiculous that I had to upgrade to an Intel Dual Core processor to keep Metastock from locking up my CPU at 100% in fast market conditions and receiving the message from Metastock that it couldn't keep up with the data flow when it, along with eSignal, was the only program running. Equis forum moderators, I would kindly appreciate it if you would forward this issue on to the developers and have them make it a top priority to figuring out a way to fix this unnecessary problem in future patches, upgrades or new Metastock releases. Thanks in advance. Regards, Ringo

Konrad, Because, unfortunately, Metastock is a huge CPU hog, even more so when "Enable Real Time Bars" is enabled. Even without "Enable Real Time Bars" enabled, Metastock is using way too much CPU resources. It is a serious flaw in Metastock's development and must be fixed. Check in your local history to make sure you don't have alot of unnecessary symobls updating. I have none in local history and Metastock was killing both my P4, 2.53 ghz and a brand new AMD 3500+ with 1 gb ddr2 ram. It finally took a dual core Pentium D processor to alleviate the 100% lockup peg and I still get 100% CPU usage spikes but they last but a split second. On my P4, my charts were lagging by up to 2 minutes in fast market conditions. You are not alone in this problem. Ringo

Ringo, Your Ram is ddr, that mean share with graphic card go to bios in windows and change for lower gaphic option , like 128 mb is look very good, and will increase your speed, I got 4 gb of memory but only 20% is shared with other application :D