youtrack-windows:2025.3.104992 Memory allocation.
Hi,
I'm trying to upgrade the memory allocation on my youtrack-windows:2025.3.104992 container that is currently 989.8 MB.
I tried to allocate more Memory via the Docker engine API and with a parameter using JAVA_OPTS but none of theses attemps worked.
I only use Docker engine via command line and not the Docker desktop.
Is there a way to upgrade the performance of the youtrack-windows container?
Thanks,
Regards,
Please sign in to leave a comment.
Hello!
The YouTrack image startup script does not use the variable
JAVA_OPTS, that is why passing the value for memory allocation in that environment variable does not have any effect.To increase the memory allocation, you need to adjust the
-Xmxdefault JVM option. You can find the detailed guidelines on how to edit the configuration file with the JVM options, here: https://www.jetbrains.com/help/youtrack/server/2025.3/configure-jvm-options.htmlWe recommend that the available memory is always larger than the Database Size without BLOBs, which you can find in the server metrics. If you have the text recognition feature enabled (it is enabled by default), the memory allocated should be bigger than the database size without BLOBs by at least 2 GB.
Don't hesitate to reach out anytime if you have any questions!
Hello,
When I display the variables from inside the container, I see that the -Xmx is set to 4GB. But from the Server metrics I still see 989.8 MB.
SERVICE_WRAPPER_JAVA_OPTS=-Xmx4g
I have restarted the container several times.
I am not an advance user of Docker I might have look at the wrong place.
Many thanks,
Regards,
Hi,
I'm Sergey from the YouTrack team.
As my colleague mentioned, YouTrack containers do not use any environment variables to allocate memory to the app, so both JAVA_OPTS and SERVICE_WRAPPER_JAVA_OPTS have zero effect on memory allocation. You need to configure the memory following the provided instructions instead.
For example, you can specify the memory value in the YouTrack config file as described here: Configure JVM Options.
Hi,
Sorry for the delayed response, my container was stocked in a boot loop so I had to scale down to 3 GB but now everything is fine.
Thanks for the support,
Regards,
Hi Leo,
Thanks for the update. I'm glad to hear that you've resolved the issue. Feel free to reach out if there's anything else we can assist you with.