Tune JVM and Tomcat parameters to improve performance, increase throughput, and reduce latency for applications deployed in EDAS ECS clusters.
Configuration levels
Parameters can be set at two levels:
| Level | Scope |
|---|---|
| Application | Applies to all application instance groups. |
| Application instance group | Applies only to a specific group. |
Instance group settings take precedence over application settings. If a group has no custom settings, the application-level settings apply.
Navigate to the configuration page
All configuration tasks start from the same entry point.
-
Log on to the EDAS console.
-
In the left-side navigation pane, choose Application Management > Applications.
-
In the top navigation bar, select a region.
-
At the top of the Applications page, select a namespace from the Microservices Namespace drop-down list.
-
Click the name of the application to manage.
-
Open the configuration page at either the application or group level:
-
Application settings:
In the Application Settings section of the Basic Information tab, configure JVM Parameters, Basic Information, or Mount Script.
-
Group settings:
-
Click the Instance Information tab.
-
Move the pointer over Group Settings next to the target group.
-
Select JVM, Tomcat, or Mount Script from the Group Settings drop-down list.
-
-
Configure JVM parameters
-
In the Application Settings section of the Basic Information tab, click Edit next to JVM Parameters.
-
Click Memory Configuration, Application, GC Policy, Tool, and Custom to configure the relevant parameters.
NoteIf the built-in options do not meet your requirements, click Custom and enter values in the Custom Parameters field.For HSF applications, the JVM -D startup configuration parameters provide additional tuning options.
-
Click Configure JVM Parameters to save.
-
Restart the application to apply the JVM parameters.
Configure Tomcat parameters
-
In the Application Settings section, click Edit next to Application Settings to open the Tomcat configuration panel.
Configure the following parameters:
Parameter Description Default Application Port Tomcat listening port. Valid range: 1024--65535. Ports below 1024 require root permissions; container configuration requires only Admin permissions. Set the port to 1024 or higher. 8080 Tomcat Context The application URL path. Context path options. -- Maximum Threads Maximum connection pool size, mapped to maxThreads. Directly affects performance—adjust with care and seek professional guidance when necessary.400 Tomcat Encoding The character encoding format for Tomcat. Valid values: UTF-8, ISO-8859-1, GBK, GB2312. ISO-8859-1 -
Click Configure Tomcat to save.
Context path options
The Tomcat Context parameter determines how the application is accessed:
| Option | Custom path required? | Resulting access path |
|---|---|---|
| Package Name | No | The name of the WAR package. |
| Root Directory | No | / |
| Custom | Yes -- specify a value in Custom Path. | The value specified in Custom Path. |
If Tomcat Context is not configured, the access path defaults to the WAR package name.
Modify application name and description
-
In the Application Settings section, click Basic Information.
-
Update the Application Name and Application Description fields.
-
Click Modify to save.