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)




"IQ feed works very well, does not have all of the normal interruptions I have grown used to on *******" - Comment from Mark
"I cannot believe what a difference it makes trading with ProphetX!" - Comment from Bruce in Los Angeles
"IQ feed is brilliant. The support is mind-bending. What service!" - Comment from Public Forum Post
"If you want customer service that answers the phone, your best bet is IQFeed. I cannot stop praising them or their technical support. They are always there for you, and they are quick. I have used ****** too but the best value is IQFeed." - Comment from Public Forum
"I like you guys better than *******...much more stable and a whole lot fewer issues." - Comment from Philip
"I "bracket trade" all major news releases and I have not found one lag or glitch with DTN.IQ feed. I am very comfortable with their feed under all typical news conditions (Fed releases, employment numbers, etc)." - Comment from Public Forum
"Can I get another account from you? I am tired of ******* going down so often" - Comment from George
"You are much better than lawyers or the phone company because you answer the phone when I call! I just love your customer service." - Comment from Isreal
"I am keeping IQFeed, much better reliabilty than *******. I may refer a few other people in the office to switch as well." - Comment from Don
"Thanks for all of your help. Great customer service deserves to be recognized which one the reasons I've been a customer of DTN for over 10 years!" - Comment from Stuart
Home  Search  Register  Login  Blogs Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTN_IQFeed on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »Product Support »DTN.IQ Client Software Support »IqFeed client crushes
Author Topic: IqFeed client crushes (9 messages, Page 1 of 1)

Ariloum
-Interested User-
Posts: 20
Joined: Oct 22, 2014


Posted: Oct 24, 2015 07:26 AM          Msg. 1 of 9
Hello,
I've written a screener which download and update last day candles by downloading historical data, I'm using a few threads connecting to iqfeed client historical data port and if I set it's amount to 100 threads(connections) iqfeed client crushes. It works well with 40 connections thread, but I need more threads to get higher rate for updating speed. I'm using iqfeed client v.5.1.3.1.

DTN_Tim Walter
-DTN Guru-
Posts: 1227
Joined: Apr 25, 2006


Posted: Oct 24, 2015 08:06 AM          Msg. 2 of 9
Good morning,

In regards to history, 18 concurrent history requests is the maximum that can be processed at any one time, so you will not be able to pull data across 100 threads without seeing lots of errors I would guess.

That said, there is a patched build that deals with a bug that is probably what you are seeing, I'll email you a link.

Tim

Ariloum
-Interested User-
Posts: 20
Joined: Oct 22, 2014


Posted: Oct 26, 2015 10:32 AM          Msg. 3 of 9
Hi Tim, thanx for your input,

I tried this patched version and looks like it works fine, need to test it for a few days.

http://prntscr.com/8vjlx0
Edited by Ariloum on Oct 26, 2015 at 10:32 AM



File Attached: QIP Shot - Screen 2015.10.26 18-28-53.png (downloaded 579 times)

DTN_Tim Walter
-DTN Guru-
Posts: 1227
Joined: Apr 25, 2006


Posted: Oct 26, 2015 10:35 AM          Msg. 4 of 9
Glad to hear it. Thanks for letting us know.

Tim

Ariloum
-Interested User-
Posts: 20
Joined: Oct 22, 2014


Posted: Oct 30, 2015 08:46 AM          Msg. 5 of 9
Sometimes I've too many errors with simultaneous history requests while I'm using 30 connections to historical service port:
E,Too many simultaneous history requests.,

Sometimes it's ok and errors are rare, but sometimes I'm getting it very often. Do you have some load balancer on your serverside which dynamically limit connections to historical service?

DTN_Tim Walter
-DTN Guru-
Posts: 1227
Joined: Apr 25, 2006


Posted: Oct 30, 2015 08:49 AM          Msg. 6 of 9
Yes, as mentioned above, there is a limit of 15 concurrent connections on pulling data from history. More than that will result in the error you are seeing. In this case, you will simply have to re-request when you have slots available, or limit your active requests to 15.

Tim
Edited by DTN_Tim Walter on Oct 30, 2015 at 09:09 AM

Ariloum
-Interested User-
Posts: 20
Joined: Oct 22, 2014


Posted: Oct 30, 2015 09:20 AM          Msg. 7 of 9
Did this limit is hardcoded or it's dynamic?
Sometimes I'm going pretty well with 30 connections with only a few errors, but sometimes I receive a horde of errors..

DTN_Tim Walter
-DTN Guru-
Posts: 1227
Joined: Apr 25, 2006


Posted: Oct 30, 2015 09:29 AM          Msg. 8 of 9
It is hardcoded, but it is related to how many are actually processing at any one time. Many requests happen in just milliseconds so it can appear that you are processing more than 15 requests with these smaller requests. But, if you did 15 requests for a large amount of tick data and those requests all took 10 seconds each to complete each, then all other requests would fail and return errors.

Tim

Ariloum
-Interested User-
Posts: 20
Joined: Oct 22, 2014


Posted: Oct 30, 2015 09:36 AM          Msg. 9 of 9
I see, thanx for the info.
I'm receiving only last few 1minute candles to update my current stock snapshot.
 

 

Time: Tue September 25, 2018 6:20 PM CFBB v1.2.0 15 ms.
© AderSoftware 2002-2003