Home  Search  Register  Login  Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »Archive (2017 and earlier) »IQFeed Developer Support »Issue with throughput
Author Topic: Issue with throughput (3 messages, Page 1 of 1)

parallelguy
-Interested User-
Posts: 12
Joined: Feb 17, 2010


Posted: May 14, 2010 09:26 AM          Msg. 1 of 3
IQFeed seems to be having issues sustaining communications above 930-1000 KB/sec and thus seems to be losing data during very high volume periods.

I'm on a 22/6mbit cable modem, and have verified that I can sustain 22mbit speeds on both tcp and udp. I am subscribed to 576 symbols, which comprises of the S&P 500, some misc etf's and stocks, and the major futures. Regional updates are enabled for all stocks.

I suspect this may be some sort of TCP window problem, as experimenting with TCP window settings on windows 2008 r2 does seem to measurably affect the peak rate I can get out of IQFeed. Unfortunately, none of them seem to perform better then the default settings. Any ideas what I might try next?

parallelguy
-Interested User-
Posts: 12
Joined: Feb 17, 2010


Posted: May 14, 2010 10:35 AM          Msg. 2 of 3
Something else just noticed: IQFeed seems to be saturating one processor worth of CPU time when receiving 900+KB/s of data (8 core machine, 4gb of ram). Memory usage does not significantly fluctuate. Could this also be a problem?

On Edit: To clarify, that is IQConnect.exe seems to saturate one core. Also, this is on 4.7.1.2 (beta).
Edited by parallelguy on May 14, 2010 at 10:55 AM

David
-DTN Evangelist-
Posts: 113
Joined: May 7, 2004

I'd rather be...


Posted: May 30, 2010 05:54 PM          Msg. 3 of 3
PG:

FWIW:

One thing that may give you some more information is to test the connection to your interface so that essentially there is no processing after each packet comes in - basically set a switch so that once quotes are coming in nothing is done with them and the socket is ready for the next data. Check out the CPU loading under this 'no loading' to see if better behaved. I suspect it may be very informative.

I found that the processing time in servicing the stream by my program affects the CPU loading of IQConnect (and obviously my program). I also discovered that the 'message pump' should not be called within the event processing called from the OnDataAvail event notification.

David

IQXP Software
http://www.iqxp.com

LiveWire Update Service
PO Box 1417
Fairfield, IA 52556
641-472-8393
http://www.livewire-cablesoft.com/
 

 

Time: Sat July 27, 2024 3:40 AM CFBB v1.2.0 11 ms.
© AderSoftware 2002-2003