Did this happen too anyone else at IB last week?

[Max E.]

I'm not running nearly as many charts as you are, but I do keep a very large watch-list up (and my position list and order lists are usually quite long, and I leave those up constantly too...)

For what it's worth, what I have noticed is:

In the past week or two, the update to TWS-LATEST is *very* laggy for me. I am staying on TWS-STABLE for now, because the responsiveness in the user interface for TWS-LATEST (starting from about August 1st?) is just unbearably slow for me. This was on two separate machines, one with 16GB RAM, and the other with 24GB RAM.

I also moved back to TWS stable which definitely made it alot faster, admittedly it was a little slow with 21 charts up on the left screens and everything else up, but now that ive killed all those charts and rebuilt my layout, im down to 5 charts total, 2 TAS, and 2 L2, and it still freezes the second i move any IB window, into 1 of those far left monitors.

So im basically stuck now only being able to have a 2 screen layout with IB, guess i could just pay for a charting service for the other 2 screens since it was mostly just charts in those windows plus the main window which i would minimised after the open and only keep there so i could pop it up once i wanted to scan and look at every thing that was moving.

Guess i should also note, its not my whole computer freezing its only TWS thats freezing, every thing else on those monitors works fine,.

 

[aquarian1]

My machine slowed down terribly when I was forced to update my software. The new bloatware ate all my memory. I went to the year old stable version and then deleted a bunch of tickers and many charts down to 6 from about 20

I also had to reduced the number of spreadsheets open.

They really need to stop doing this.

 

[aquarian1]

In case it helps
TWS running slowly
https://www.interactivebrokers.com/...guidebook/priceriskanalytics/custommemory.htm

Open topic with navigation
You are here: Price/Risk Analytics > IB Risk NavigatorSM > Increase Memory Size for TWS
Increase Memory Size for TWS

Advanced users who manage large portfolios (over 500 stock or 100 options positions) or who simultaneously use more than 15 chart windows may need to manually increase the amount of memory allotted to TWS to accommodate the higher demands needed by both TWS and the Risk Navigator to handle this kind of heavy load.

Modifying the memory size requires that you open, edit and save the tws.vmoptions file.
Find the tws.vmoptions File

Standard Download: If you downloaded standard TWS software (Latest, Beta or stable) you will find this file in the Jts folder which is typically in the C:\ directory on Windows/Linux machines, and in ~/ on the Mac.

Note: If you didn't specifically find and download the Offline TWS, you are using the standard TWS software.

For example, you will likely find the file in C:\Jts\tws.vmoptions (Windows and Linux) and in ~/Jts/tws.vmoptions (Mac). If you are having trouble finding this file among all of the "tws" files in Windows file explorer, look in the "Type" column for VMOPTIONS File in all uppercase letters.

Offline Download: If you downloaded the Offline TWS software, you will find this file in a sub directory of the Jts folder, named for the build version you downloaded.

For example, if you installed Offline TWS Latest when the latest version was 955.4, you will likely find the file in C:\Jts\955\tws.vmoptions (Windows and Linux) and in ~/Jts/tws-955.vmoptions (Mac).
Edit the tws.vmoptions File

1. Open the file, and find the line that looks like: -Xmx768m. This defines the memory size currently being used by TWS. In this example, it is 768 MB.

Note: If you're running Window 10, consider opening and editing the file directly in Notepad. To open Notepad, right-click the Start button and select Run. Type "notepad." Use the File>Open menu in Notepad and in the Files of Type field change the filter to All Files. Navigate to C:/jts and find the tws.vmoptions file. Make edits as shown then Save the file.

2. Modify the size (in MB). We recommend not to go above 2 GB (or 2000 MB) as this will likely degrade your machine's overall performance.

3. Move this memory size line BELOW the line that says: ### keep on update. Otherwise, the setting will revert to the default value when the version is updated.

The body of the file will look something like the below when you're done (note the highlighted lines at the bottom of the file):


4. Save the file.

Check that the memory has been upgraded the next time you log into TWS. From the Help menu select About and check the max heap size in the Java Version section.



-------