This container uses significantly more RAM than the one from the nzbhydra2 repository

[xconverge]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

On initial startup, this container uses nearly double the RAM that the hydradocker image uses (https://github.com/theotherp/nzbhydra2/pkgs/container/hydradocker)

I scanned this note https://github.com/theotherp/nzbhydra2/blob/master/nativeNotes.md

It also mentions that there is no need for java to be installed to run as well (when it seems to be installed in this image https://github.com/linuxserver/docker-nzbhydra2/blob/master/Dockerfile#L21), but I imagine it is easier to just keep this for migrating from an older version and to not break too much of the logic for backwards compatibility? I wonder if there is some fallback happening due to it being installed, not sure...

I am willing to help dig into this, but nothing obvious jumped out at me other than the potential for the binaries to be different between the releases and what they compile into the docker image/flags they set

Expected Behavior

Similar resource consumption since they are the same application...

Steps To Reproduce

Run 1 image, check RAM, run other image, check RAM

Environment

- OS: Debian
- How docker service was installed: docker-compose

CPU architecture

x86-64

Docker creation

image: ghcr.io/linuxserver/nzbhydra2 or image: ghcr.io/linuxserver/nzbhydra2:dev-v5.2.0-ls134 vs

image: ghcr.io/theotherp/hydradocker:latest

Container logs

n/a

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[xconverge]

I have no ideas on what this could be...

this image shortly after startup uses ~500-550MB...the hydradocker image is ~200-250MB

[xconverge]

Here is a short snippet from top in the 2 containers 🤷

Hydradocker:

Linuxserver image:

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue is locked due to inactivity