I was wondering if anyone can help me solve the issues with memory spikes in IQCONNECT. For months I have been getting the "Out Of Memory" warning with IQConnect. On previous attempts to get to the root of the problem I was told that the issue was that my machine wasn't processing the quotes quickly enough, that may have been true in the past but I have worked to get rid of all latency issues on my part. Today I ran IQConnect starting at 09:48 with 3 minute charts of 560 symbols. It worked like an absolute charm until for most of the day ranging between 41MB and 45MB of RAM. At 3:45 pm it spiked above 50MB and I didn't receive any more quotes until 3:58 PM when I got the 3:48 pm quotes. There was no spike in the RAM used by my program and I use IB TWS as my broker/trading platform. Can ANYONE please help me to solve this issue? PLEASE I've worked very hard on this program and I just want it to work.

Rich,

It sounds like the app stopped doing anything for a period of time and understanding that will be the first step in trying to understand what is going on for you.

To confirm, have you upgraded to the 5.2 code base yet? If so, could you please download and test with that code, assuming that it continues to happen (which I expect it will, but we have some better logging there), could you enable all Level 1 logging during the next period that you are seeing no data flow? Also, if the quotes stop coming into your app and you open IQWatchQuote, are the quotes up to date or flowing there?

Tim

I did upgrade the client to 5.2, this morning. In terms of the protocol I didn't change my code except to change the protocol in my code from 5.1 to 5.2. I didn't use any level one quotes today, and when it spiked I didn't attempt to get quotes from IQWatchQuote or anywhere else I was seeing if it would eventually work itself out, but like I said the next time I got a quote it was 10 minutes delayed. I don't watch the quotes come in on the UI for obvious reasons so I can only see whats in the db after the fact.
Edited by Rich_B on Jan 25, 2016 at 03:24 PM

Well let's at least try watchquote next time and if we can enable some logging. With the information I have there is no way for me to know how or why it got stuck unfortunately. How often are you writing to the database btw, sometimes issues can happen there.

Tim