search

jlesage / docker-jdownloader-2

Docker container for JDownloader 2
MIT License
820 stars 71 forks source link

[Bug] ~4% CPU usage in idle #188

Closed somera closed 10 months ago

somera commented 11 months ago

Current Behavior

When I start the container I see 2-6% (average is ~4%) CPU usage in idle.

image

And I have no open tab in browser.

image

I can't see why. All my other containers use ~0,5% CPU in idle.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

Container creation

docker run -d \ --network=host \ --name=jdownloader-2 \ -p 5800:5800 \ -v ./config:/config:rw \ -v ./downloads:/output:rw \ jlesage/jdownloader-2

Container log

╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
    │                                                                      │
    │ Application:           JDownloader 2                                 │
    │ Application Version:   n/a                                           │
    │ Docker Image Version:  23.11.2                                       │
    │ Docker Image Platform: linux/amd64                                   │
    │                                                                      │
    ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯
[cont-init   ] 89-info.sh: terminated successfully.
[cont-init   ] all container initialization scripts executed.
[init        ] giving control to process supervisor.
[supervisor  ] loading services...
[supervisor  ] loading service 'default'...
[supervisor  ] loading service 'logrotate'...
[supervisor  ] loading service 'app'...
[supervisor  ] loading service 'gui'...
[supervisor  ] loading service 'nginx'...
[supervisor  ] loading service 'xvnc'...
[supervisor  ] loading service 'certsmonitor'...
[supervisor  ] service 'certsmonitor' is disabled.
[supervisor  ] loading service 'openbox'...
[supervisor  ] loading service 'logmonitor'...
[supervisor  ] service 'logmonitor' is disabled.
[supervisor  ] all services loaded.
[supervisor  ] starting services...
[supervisor  ] starting service 'xvnc'...
[xvnc        ] Xvnc TigerVNC 1.13.1 - built Nov 17 2023 22:53:44
[xvnc        ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
[xvnc        ] See https://www.tigervnc.org for information on TigerVNC.
[xvnc        ] Underlying X server release 12014000
[xvnc        ] Fri Dec 22 16:20:09 2023
[xvnc        ]  vncext:      VNC extension running!
[xvnc        ]  vncext:      Listening for VNC connections on /tmp/vnc.sock (mode 0660)
[xvnc        ]  vncext:      Listening for VNC connections on all interface(s), port 5900
[xvnc        ]  vncext:      created VNC server for screen 0
[supervisor  ] starting service 'nginx'...
[nginx       ] Listening for HTTP connections on port 5800.
[supervisor  ] starting service 'openbox'...
[supervisor  ] starting service 'app'...
[supervisor  ] all services started.
[xvnc        ] Fri Dec 22 16:20:19 2023
[xvnc        ]  Connections: accepted: /tmp/vnc.sock
[xvnc        ]  SConnection: Client needs protocol version 3.8
[xvnc        ]  SConnection: Client requests security type None(1)
[xvnc        ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc        ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[xvnc        ] Fri Dec 22 16:20:36 2023
[xvnc        ]  VNCSConnST:  closing /tmp/vnc.sock: Clean disconnection
[xvnc        ]  EncodeManager: Framebuffer updates: 3
[xvnc        ]  EncodeManager:   Tight:
[xvnc        ]  EncodeManager:     Solid: 5 rects, 2.0736 Mpixels
[xvnc        ]  EncodeManager:            80 B (1:103681 ratio)
[xvnc        ]  EncodeManager:     Bitmap RLE: 1 rects, 160 pixels
[xvnc        ]  EncodeManager:                 68 B (1:9.58824 ratio)
[xvnc        ]  EncodeManager:   Total: 6 rects, 2.07376 Mpixels
[xvnc        ]  EncodeManager:          148 B (1:56048.1 ratio)
[xvnc        ]  Connections: closed: /tmp/vnc.sock
[xvnc        ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc        ]  ComparingUpdateTracker: (1:-nan ratio)
[xvnc        ]  Connections: accepted: /tmp/vnc.sock
[xvnc        ]  SConnection: Client needs protocol version 3.8
[xvnc        ]  SConnection: Client requests security type None(1)
[xvnc        ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc        ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[xvnc        ] Fri Dec 22 16:32:34 2023
[xvnc        ]  VNCSConnST:  closing /tmp/vnc.sock: Clean disconnection
[xvnc        ]  EncodeManager: Framebuffer updates: 3459
[xvnc        ]  EncodeManager:   Tight:
[xvnc        ]  EncodeManager:     Solid: 587 rects, 9.84628 Mpixels
[xvnc        ]  EncodeManager:            9.17188 KiB (1:4194.23 ratio)
[xvnc        ]  EncodeManager:     Bitmap RLE: 1.825 krects, 139.973 kpixels
[xvnc        ]  EncodeManager:                 49.8643 KiB (1:11.3941 ratio)
[xvnc        ]  EncodeManager:     Indexed RLE: 23.47 krects, 5.04859 Mpixels
[xvnc        ]  EncodeManager:                  2.24928 MiB (1:8.68164 ratio)
[xvnc        ]  EncodeManager:   Tight (JPEG):
[xvnc        ]  EncodeManager:     Full Colour: 987 rects, 4.65747 Mpixels
[xvnc        ]  EncodeManager:                  3.57758 MiB (1:4.96932 ratio)
[xvnc        ]  EncodeManager:   Total: 26.869 krects, 19.6923 Mpixels
[xvnc        ]  EncodeManager:          5.88451 MiB (1:12.818 ratio)
[xvnc        ]  Connections: closed: /tmp/vnc.sock
[xvnc        ]  ComparingUpdateTracker: 1.21257 Gpixels in / 15.3177 Mpixels out
[xvnc        ]  ComparingUpdateTracker: (1:79.1612 ratio)

Container inspect

No response

Anything else?

No response

somera commented 11 months ago

Screenshot from doozle

image

jlesage commented 11 months ago

A small amount of CPU usage at idle is expected for this kind of application.

All my other containers use ~0,5% CPU in idle.

Probably because there are not implementing a full-GUI application ?

somera commented 10 months ago

Probably because there are not implementing a full-GUI application ?

Probably. ;)

But in Idle? I close this.

jlesage commented 10 months ago

Compared to other GUI applications I have (using the same baseimage), I see that JDownloader container is using a little bit more CPU: about 4%, while others are more around 1% or less.

So I assume that JDownloader itself makes the difference. Did you check on the JDownloader's forum to see if this has been discussed?

somera commented 10 months ago

@jlesage I check this in the new year.