Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Non-Tech : Quote.com QCharts -- Ignore unavailable to you. Want to Upgrade?

To: peter n matzke who wrote (4257)	11/9/1999 8:46:00 AM
From: Matthew L. Jones	Respond to of 17977

Peter, I would suggest that perhaps you have no idea what I watch. I trade for a living. All day, every day. I watch two separate quote systems all day long. I watch the following future symbols: ES99Z, DX99Z, NQ99Z, US99Z, as well as a host of other indicators, indices, and symbols. I am sorry that you have had problems with your charts, I have not had any. Occasionally, when pulling up a chart which requires a lot of data, I might get a few second delay while it pulls up the data, but otherwise I've had nothing but superior results since starting about a month ago. I typically use 30 minute and 5 minute charts with Stochastics, Bollinger bands, 2 moving averages, ADX, and RSI. Generally candle sticks. I never use 1 minute bars. I never have more than two charts open at once (screen space) and two watch lists and time and sales for the S&P E-mini. I rarely get on the Mountainview server, however (that seems to be where a lot of the problem was). If the feed from Q-charts was the problem, it was not present on all of the servers. I had very good performance all day on Stclara server (slowed a couple of times to about 1.14 seconds and I switched to Jersey). I would suggest using a program (free to download) called NeoTrace (neotrace.com). It will continually ping your connection (every 5 seconds) and give you a list of time at each node. I am normally connecting through about 12-13 nodes. If there is a data bottle neck, it will give you a print out of the location, the speed, and the IP address of the failing link in the data chain. Maybe this will help you to pinpoint the problem. BTW, I have never experience a single gap in data, so I am not sure how to address that problem. Good luck today. Matt