<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic For Alfresco Services Hosted in Docker Container - Use -Xmx vs - XX:MaxRAMPercentage ? in Alfresco Forum</title>
    <link>https://connect.hyland.com/t5/alfresco-forum/for-alfresco-services-hosted-in-docker-container-use-xmx-vs-xx/m-p/118961#M32788</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hello,&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We recently had a Hyland Coaching session. We utilize Docker Containers and Docker Compose with Swarm.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I went through every step file and every environment. Created the the JVM Allocation Notes documentation (See Attached Documentation)&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The Hyland Documentation (&lt;SPAN&gt;&lt;A href="https://docs.alfresco.com/content-services/7.2/config/repository/#tune-the-jvm" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.alfresco.com/content-services/7.2/config/repository/#tune-the-jvm&lt;/A&gt;) is suggesting that we utilize&amp;nbsp;Use -Xmx to specify the explicit maximum heap size rather than what we are currently using&amp;nbsp;- XX:MaxRAMPercentage in order to be dynamic and specify a percentage of ram of the container rather than a hard coded Ram if we allocate more somemory to the container.&amp;nbsp;XX:MaxRAMPercentage seems to be&amp;nbsp; the standard for JVM in containers.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Notes on parameters suggested&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Use -Xmx to specify the maximum heap size&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Use -Xms to specify the initial Java heap size&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Use -Xss to set the Java thread stack size&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Suggested by Hyland&lt;BR /&gt;- For 50 concurrent or up to 500 casual users 2.0 GB JVM RAM 2x server CPU (or 1xDual-core)&lt;BR /&gt;- For 100 concurrent users or up to 1000 casual users 4.0 GB JVM RAM 4x server CPU (or 2xDual-core)&lt;BR /&gt;- For 200 concurrent users or up to 2000 casual users 8.0 GB JVM RAM 8x server CPU (or 4xDual-core)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Notes on parameter we are using :&lt;BR /&gt;&lt;BR /&gt;- XX:MinRAMPercentage - The MinRAMPercentage parameter, unlike its name, allows setting the maximum heap size for a JVM running with a small amount of memory (less than 200MB).&lt;BR /&gt;- XX: InitialRAMPercentage: This parameter sets the initial heap size as a percentage of the total memory of a physical server or container. For instance, if you set -XX:InitialRAMPercentage=50.0 on a 1 GB server, the initial heap size will be around 500 MB (50% of 1 GB).&lt;BR /&gt;- XX:MaxRAMPercentage - Similar to MinRAMPercentage, this parameter also affects the maximum heap size. It allows specifying the percentage of available RAM for heap allocation, making it useful in containerized environments&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Question(s):&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;- Although we are not setting -Xms1G or -Xmx2G for most of the ram sizes we are using - XX:MinRAMPercentage and XX:MaxRAMPercentage which allows us to adjust for the overall container's memory. It is suggested to use a percentage. Has anyone noticed that there is a issue with using&amp;nbsp;XX:MinRAMPercentage with containers as opposed to --Xmx2G etc ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Best,&lt;BR /&gt;&lt;BR /&gt;Sean&lt;/P&gt;</description>
    <pubDate>Mon, 24 Jun 2024 21:33:32 GMT</pubDate>
    <dc:creator>finlaysons</dc:creator>
    <dc:date>2024-06-24T21:33:32Z</dc:date>
    <item>
      <title>For Alfresco Services Hosted in Docker Container - Use -Xmx vs - XX:MaxRAMPercentage ?</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/for-alfresco-services-hosted-in-docker-container-use-xmx-vs-xx/m-p/118961#M32788</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello,&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We recently had a Hyland Coaching session. We utilize Docker Containers and Docker Compose with Swarm.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I went through every step file and every environment. Created the the JVM Allocation Notes documentation (See Attached Documentation)&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The Hyland Documentation (&lt;SPAN&gt;&lt;A href="https://docs.alfresco.com/content-services/7.2/config/repository/#tune-the-jvm" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.alfresco.com/content-services/7.2/config/repository/#tune-the-jvm&lt;/A&gt;) is suggesting that we utilize&amp;nbsp;Use -Xmx to specify the explicit maximum heap size rather than what we are currently using&amp;nbsp;- XX:MaxRAMPercentage in order to be dynamic and specify a percentage of ram of the container rather than a hard coded Ram if we allocate more somemory to the container.&amp;nbsp;XX:MaxRAMPercentage seems to be&amp;nbsp; the standard for JVM in containers.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Notes on parameters suggested&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Use -Xmx to specify the maximum heap size&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Use -Xms to specify the initial Java heap size&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Use -Xss to set the Java thread stack size&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Suggested by Hyland&lt;BR /&gt;- For 50 concurrent or up to 500 casual users 2.0 GB JVM RAM 2x server CPU (or 1xDual-core)&lt;BR /&gt;- For 100 concurrent users or up to 1000 casual users 4.0 GB JVM RAM 4x server CPU (or 2xDual-core)&lt;BR /&gt;- For 200 concurrent users or up to 2000 casual users 8.0 GB JVM RAM 8x server CPU (or 4xDual-core)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Notes on parameter we are using :&lt;BR /&gt;&lt;BR /&gt;- XX:MinRAMPercentage - The MinRAMPercentage parameter, unlike its name, allows setting the maximum heap size for a JVM running with a small amount of memory (less than 200MB).&lt;BR /&gt;- XX: InitialRAMPercentage: This parameter sets the initial heap size as a percentage of the total memory of a physical server or container. For instance, if you set -XX:InitialRAMPercentage=50.0 on a 1 GB server, the initial heap size will be around 500 MB (50% of 1 GB).&lt;BR /&gt;- XX:MaxRAMPercentage - Similar to MinRAMPercentage, this parameter also affects the maximum heap size. It allows specifying the percentage of available RAM for heap allocation, making it useful in containerized environments&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Question(s):&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;- Although we are not setting -Xms1G or -Xmx2G for most of the ram sizes we are using - XX:MinRAMPercentage and XX:MaxRAMPercentage which allows us to adjust for the overall container's memory. It is suggested to use a percentage. Has anyone noticed that there is a issue with using&amp;nbsp;XX:MinRAMPercentage with containers as opposed to --Xmx2G etc ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Best,&lt;BR /&gt;&lt;BR /&gt;Sean&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jun 2024 21:33:32 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/for-alfresco-services-hosted-in-docker-container-use-xmx-vs-xx/m-p/118961#M32788</guid>
      <dc:creator>finlaysons</dc:creator>
      <dc:date>2024-06-24T21:33:32Z</dc:date>
    </item>
  </channel>
</rss>

