IB TWS taking a lot of memory

Quote from pfranz:

Supposing that the problem is historical data download,I don't understand why multicharts has to do it so much.
I plot charts only from data stored on disk,and use data downloading only to complete the missing data in the disk.this way downloads are not so many.
More...
That's exactly the way Multicharts handles it: historical data is retrieved from locally stored data and only the "gaps" are downloaded, when this option is enabled.

Quote from pfranz:

Before asking IB maybe you could first of all try java 1.6 instead of 1.7,then windows 7 32bit or any other windows version you can have access to.
More...
I tried both Java 1.6 and 1.7. According to IB support, Java 1.7 is the recommended version. I tried installing only Java 32 bit, only 64 bit, 32/64 bit in parallel (which is recommended by IB and is my actual configuration).
All to no avail.

I've already provided IB with tons of logs. Supposedly, since the "heavy traders" normally do not upgrade their TWS / Gateway unless they are forced to, the issue is just not that prevalent at the moment as only few traders use TWS / Gateway 933.5+.

For the moment, I will stick with TWS 932.4.
 
Quote from pfranz:

Thanks for your information,ddecker,but it seems you didn't read what regulus wrote.
1) The problem is just from 933.5 onward, so 930.5 is known to work right. If you want to help, why don't you try on linux, version 933.5 or later and carefully watch memory consumption?
[/B]
More...

Sorry, I meant version 938.1. Below is a screenshot of gateway 938.1 heap usage over a day running on Debian 6.0 (32-bit) with Oracle JVM 1.6.0_45. For my application at least which admittedly isn't very demanding, I don't see any issue.

I run with the following Java switches:

-Dsun.java2d.noddraw=true
-Xmx512M

I'm not sure how much you know about Java, but if you can I'd recommend setting the maximum heap to 1G or so and turning on GC logging so you can see what is actually going on. At the very least, it will give you some evidence to complain to IB with and some material to help them correct any issue.
 

Attachments

Well,if the only thing that changes between us and regulus is the 64bit type OS,maybe there lies the problem.
As I wrote,I know java very little,and I don't think customers (who are not supposed to be programmers) are expected to dig into GC.
I won't ask IB as I don't have problems,I tried 933.5 and will try 938.1 just to help regulus and make sure that my system works fine.
As I wrote in the past, 50-80 MB memory usage for a TCP relay is way too much,I think IB should make it lighter.
I tried Firetip, a complete java trading application,and while using DOM and charts,memory usage was 100 MB
 
Totally agree it shouldn't be necessary and in most cases thankfully it's not. Unfortunately for regulus, it seems the next logical step if he wants to see what activity is creating the issue.

Regulus, in case you're interested to take a look, it's quite easy. Simply add the following command line switches when invoking the client:

-Xloggc:mygc.log
-verbose:gc
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-XX:+PrintHeapAtGC

This will create a file called mygc.log that includes all of the allocation/collection/heap etc. information over the life of the app. You can then use any number of apps to view the details. I prefer HPjmeter, which you can download from the HP website.
 
Quote from ddecker:

Sorry, I meant version 938.1. Below is a screenshot of gateway 938.1 heap usage over a day running on Debian 6.0 (32-bit) with Oracle JVM 1.6.0_45. For my application at least which admittedly isn't very demanding, I don't see any issue.
More...

Maybe you want to try to plot in your application some charts of tick data for some Futures intruments (CL, GC, YM etc.) with a historical data range of at least several days, since I have experienced the issue only under these specific conditions.


Quote from pfranz:

Well,if the only thing that changes between us and regulus is the 64bit type OS,maybe there lies the problem.
More...

I made some test runs on a dissimilar Win XP 32 bit workstation with Multicharts 32 and plotted some Futures charts of tick data. Same issue here, memory usage increases continuously and TWS 933.5 freezes after some hours. No issues with TWS 932.4
However, the effect is slightly different to the memory leak that occurs in a 64 bit environment: in 32 bit, TWS first looses data connection to IB (purple grid), and then will finally freeze. Reproduced that several times.
 
Quote from regulus:

Maybe you want to try to plot in your application some charts of tick data for some Futures intruments (CL, GC, YM etc.) with a historical data range of at least several days, since I have experienced the issue only under these specific conditions.




I made some test runs on a dissimilar Win XP 32 bit workstation with Multicharts 32 and plotted some Futures charts of tick data. Same issue here, memory usage increases continuously and TWS 933.5 freezes after some hours. No issues with TWS 932.4
However, the effect is slightly different to the memory leak that occurs in a 64 bit environment: in 32 bit, TWS first looses data connection to IB (purple grid), and then will finally freeze. Reproduced that several times.
More...

All of my points are regarding the Gateway, not TWS. I don't use any historical data methods within my application. Again, if you want to understand what's happening, suggest you profile/log.
 
regulus,
I use only 1 sec. data,so I'm in the same case as you are.I have 1 GB of memory and set java heap to 96 MB.
So I don't understand why my problem is much smaller than yours (actually I have no problem)
 
Quote from ddecker:

Again, if you want to understand what's happening, suggest you profile/log.
More...

I tried to integrate the Java log commands you suggested into the TWS shortcut target field, but there is a limitation of characters. Then I tried to start TWS via batch file, but I am not sure how to set the Java class path correctly. I will have another try later on.
 
You must log in or register to reply here.
Back
Top