why doe IB's TWS eat up an extra 200 meg during the day

max401 · Jan 17, 2007

Quote from illiquid:

I am getting the same thing, has only occurred since the forced upgrade. Quotes just stop moving after a while, minimizing fixes it. No charts or any other extras here either, just a list of quotes.

Anyone have an idea if they are already looking into this issue?

I've got Build 865.7 and it runs fine. Machine has 1 gig of memory.

illiquid · Jan 17, 2007

Quote from max401:

I've got Build 865.7 and it runs fine. Machine has 1 gig of memory.

I thought that minimizing fixed the freezing, but only certain tickers kept moving, others did not, despite exchange feed. My euro was moving ok, but my cad wasn't updating -- scary stuff, never seen that before.

max401 · Jan 17, 2007

Quote from illiquid:

I thought that minimizing fixed the freezing, but only certain tickers kept moving, others did not, despite exchange feed. My euro was moving ok, but my cad wasn't updating -- scary stuff, never seen that before.

I have the same tickers in IB paired with eSignal so I know they're moving correctly, although there are the occaisional price discrepancies between the two.

illiquid · Jan 17, 2007

Yeah if it wasn't for my other feed, I would have sat there for 10 minutes and not realized it wasn't adjusting (cad can be slow sometimes).

I can't get the problem to repeat, so might have been just a fluke.

stock777 · Jan 17, 2007

Quote from kiwi_trader:

But FWIW, I got rid of every problem I had by ugrading to a Core2Duo E6600 with 2G of matched 800MHz RAM. Fast. Who cares about 200M anymore (I run Sierrachart on a ram disk just to reduce disk wear). Reliable as you could want.

I'm happy for you , but I upgraded a year ago and am in no mood to do it again.

I could add a gig of ram, to the existing gig but that would be a band aid on what looks like
a memory leak. And its not the memory I'm worried about, the TWS stops responding well.

I'll try to work with IB as they requested to figure out what the issue is.

Oh yeah, If I reformatted and reinstalled every time there was a problem like this, I'd have done so about 200 times over the last 20 years instead of the NONE times I did that.

illiquid · Jan 17, 2007

Quote from illiquid:

Yeah if it wasn't for my other feed, I would have sat there for 10 minutes and not realized it wasn't adjusting (cad can be slow sometimes).

I can't get the problem to repeat, so might have been just a fluke.

Just to update, this specific incident of certain tickers running while others stayed stuck seems to be related to my broadband connection hiccuping and tws reconnecting -- a restart of tws now seems necessary after disconnect.

kiwi_trader · Jan 17, 2007

Quote from kiwi_trader:

But if you want to get it to "contract" again try this.

Option 1.
Open your TWS windows. Then minimize them. Then open again and u should be at start point of memory use.

Option 2.
Download FreeRAM XP Pro. When you run it it will force tws to give back the "spare" stuff its holding for just in case. Run it as lightly as you can or it will slow things down as they have to regain the memory they gave back.

I'm glad you're happy for me ... but if you don't want to spend $100 for another gig did you try either of these suggestions for taming the expansion.

Bitstream · Jan 17, 2007

volumes seem totally wacked on the new built, stays normal 'till u refresh then bars shoot up.

nq shows avg volume for every 5min bar at 750k.

dunno if it is just me.

max401 · Jan 17, 2007

Quote from Bitstream:

volumes seem totally wacked on the new built, stays normal 'till u refresh then bars shoot up.

nq shows avg volume for every 5min bar at 750k.

dunno if it is just me.

The real solution is use a separate vendor for charts.

max401 · Jan 17, 2007

Quote from stock777:

Oh yeah, If I reformatted and reinstalled every time there was a problem like this, I'd have done so about 200 times over the last 20 years instead of the NONE times I did that.

Then one possibility is that another program is conflicting with TWS. Sometimes this can be pinned down by remembering what programs may have been installed around the time the problem started.

I would try an uninstall/reinstall of TWS first. Then try and uninstall the last several programs (or the ones that you may remember installing around the time the problem started) that were put on the machine.

Otherwise, worst case, you format the drive, do a clean OS install and start reinstalling the most important programs only. In my case it would be TWS, Firefox and Thunderbird. Then add the other programs in order of importance. If the glitch reappears you have the source of the problem.