DTN IQFeed, DTN.IQ, DTN ProphetX Support Forums

Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)

"I used to have *******, but they are way more money for the same thing. I have had no probs with data from DTN since switching over." - Comment from Public Forum Post

"I've never had DTN go out on me since switching. ******* would go down a couple times every month when I was using them." - Comment from Bryce in AL.

"IQ feed is brilliant. The support is mind-bending. What service!" - Comment from Public Forum Post

"I just wanted to let you know how fast and easy I found it to integrate IQFeed into our existing Java code using your JNI client. In my experience, such things almost never go so smoothly - great job!" - Comment from Nate

"There is no doubt that IQFeed is the best data provider. I am very satisfied with your services. And IQFeed is the only one that I would recommend to my friends. Now, most of them are using your product in China." - Comment from Zhezhe

"I cannot believe what a difference it makes trading with ProphetX!" - Comment from Bruce in Los Angeles

"Everything is working amazing now. I'm already impressed with the true-tick feed of IQFeed and it's ability to support my 480 symbol layout." - Comment from Tyler via Email

"IQFeed version 4 is a real screamer compared to anything else I have seen." - Comment from Tom

"Everything is working great with the API. I love it." - Comment from Calvin

"DTN has never given me problems. It is incredibly stable. In fact I've occasionally lost the data feed from Interactive Brokers, but still been able to trade because I'm getting good data from DTN." - Comment from Leighton

Home

Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather

DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter

»Forums Index »Archive (2017 and earlier) »Data and Content Support »Q record corruption, happening less?

Author	Topic: Q record corruption, happening less? (5 messages, Page 1 of 1)
kdresser -Interested User- Posts: 71 Joined: Nov 25, 2004	Posted: May 25, 2005 03:23 PM Msg. 1 of 5 Lately I've noticed a big drop in occurences of catastrophic Q record corruption. I have added extra threads in my receiver to handle file logging (in addition to a receiving thread). Is this what has improved mattters, or are there changes external to me that are contributing favorably? What have others' experiences been lately? BTW, I'm still sometimes (but less often as well) experience days when there are LOTS of otherwise OK looking pre-market Q records that have a missing HH:MMx field. What is the cause (and cure, if any) for these? So far, I've been ignoring them because they seem to become normal once the the regular session opens. All of this is about NASDAQ symbols. TIA for any comments.
DTN_Jay_Froscheiser -VP, Product Operations- Posts: 1746 Joined: May 3, 2004 DTN IQFeed/DTN.IQ/DTN NxCore	Posted: May 26, 2005 09:18 PM Msg. 2 of 5 I would be interested to see if you have the same issues as before with the new beta client. It should not see the corruption issues of past builds. Please report back with your findings! Jay Froscheiser DTN - Trading Markets
kdresser -Interested User- Posts: 71 Joined: Nov 25, 2004	Posted: May 27, 2005 10:07 AM Msg. 3 of 5 I'm trying the new client today. I put it on a 1GHz 512MB W2K machine I use for other things (development mostly). It is connected via wireless. The memory useage was above the real amount so swapping was happening. Watched an interleaved 1/2 of the top 1000 naz stocks. Today the open peaked, as usual, with 180 KB/sec into my app (measured every deciminute). I ran other stuff (including very heavy local TCPIP traffic) that hogged the cpu, causing the input to my app to stop completely for a deciminute or so. When the hog was removed, the TCPIP traffic spiked in recovery as buffered data flowed again. No corrupted Q records occured through all this. Looks like that problem has been fixed. I'll keep watching for the missing HH:MMx problem. Thanks for the improvements!
kdresser -Interested User- Posts: 71 Joined: Nov 25, 2004	Posted: May 31, 2005 07:59 AM Msg. 4 of 5 This morning, testing the new beta, I'm receiving many Q records without a HH:MMx field.
kdresser -Interested User- Posts: 71 Joined: Nov 25, 2004	Posted: Jun 6, 2005 07:33 AM Msg. 5 of 5 This morning, from 0815h to 0830h, received 900 Q records with no HH:MMx field. From streaming quote tcp/ip, not using new beta connector. Watching 467 naz symbols.