Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High CPU-Usage on TWS Desktop #129

Closed
handelsmeisterei opened this issue Jul 1, 2024 · 2 comments
Closed

High CPU-Usage on TWS Desktop #129

handelsmeisterei opened this issue Jul 1, 2024 · 2 comments
Labels
wontfix This will not be worked on

Comments

@handelsmeisterei
Copy link

tws-desktop (I am on 10.28) has a very high CPU-Usage. Docker stats reports about 150% on my cloud machine (both paper and live are running). When I analyse the processes running (htop) I see several instances of /tmp/JxBrowser/7.29/chromium ... which are responsible for the high CPU load.

Are they even needed for TWS Desktop? Only case I could imagine is, when the user wants to get Contract details and then the browser opens. In my opinion this feature is not worth the performance usage. Is it possible to start TWS without the browser?

@gnzsnz
Copy link
Owner

gnzsnz commented Jul 1, 2024

i'm using 10.19 (stable) for the same reason, AFAIK those chromium instances are launched by TWS. Stable is using the same chromium instances, so not sure if it's chromium to blame. I have noticed that stable cpu consumption is significantly lower.

i don't know any way to controll chromium, if you find something please let me know.

I think that the reason might be the "advanced charts", but it's hard to tell.

if there is anything that can be done on the image I'm happy to give it a look, but i'm afraid that is a problem with TWS itself.

@handelsmeisterei
Copy link
Author

I thought that perhaps chromium could simply be not installed in the dockerfile. But upon inspection, I realised that it will not be installed in the Dockerfile and will be started from within the TWS installation?! If so, I have no idea how this can be avoided (and not doing some hack that always kills all chromium instances)

@gnzsnz gnzsnz added the wontfix This will not be worked on label Jul 10, 2024
@gnzsnz gnzsnz closed this as completed Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants