When we moved from version 9 of TWS to version 10 we experienced generally slightly longer startup and restart times with the occasional very long delay. TWS and any open windows appeared to be frozen during these times, so we ran some network traces to see what is going on between TWS and the "outside" world.
First of all, during startup and restart, V10 TWS performs many more interactions with IBKR than what comparable V9 TWS would do. But the biggest impact on startup time in general and the cause of all very long startup times was downloading, installing, and starting JxBrowser.
While TWS/IBGW are still fundamentally Java 8 programs (and there is nothing wrong with that since Java 8 is a long-term support version along with Java 11, and Java 17), IBKR continuously upgrades the JavaFX GUI technology they use. And they take advantage of JxBrowser, a complete Chromium browser that is installed in /tmp/JxBrowser (on Linux). The current version 7.26 is just shy of 400MB when installed so it is no surprise that downloading, installing, and starting that browser may take some time. At least the peak delays are somewhat independent of how fast your server is.
We have not analyzed what exactly triggers the download and installation during startup (other than cases after system reboot when /tmp is empty) and under what circumstances TWS reuses and existing installation, but we have occasionally seen multiple versions installed by the end of the week.
I guess that was the long way of saying that peak startup times can be very long for TWS V10 and timeouts might have to increased considerably, as Richard suggested.
´³¨¹°ù²µ±ð²Ô
On Wed, Jun 7, 2023 at 09:49 AM, Kevin Jameson wrote:
Thank you. I thought it might be a slow-machine timeout (I'm on AWS), but I was kind of following the instructions "Don't change anything below this line!" :-)
I will increase my timeout if it happens again.
