sccc131 opened a new issue, #1295: URL: https://github.com/apache/maven-mvnd/issues/1295
### New feature, improvement proposal Deploy the Jenkins 2.4.8.1 container using Docker. Configure the environment variable mvnd within the container. Executing `mvnd -v` inside the container will create a daemon process. The following is the mvnd.properties ：configuration: mvnd.keepAlive = 60000 ms mvnd.minHeapSize = 256M mvnd.maxHeapSize = 512M mvnd.jvmArgs=-Xmx512m -Xms256m mvnd.minThreads = 4 mvnd.threads=4 mvnd.minIdleDaemons=2 mvnd.idleTimeout=2147483647 mvnd.duplicateDaemonGracePeriod = 3600 seconds mvnd.expirationCheckDelay = 60 seconds I found that only when the daemon process is created in advance (`mvnd -v` is executed in advance within the container), will the mvnd compilation speed triggered by the Jenkins pipeline be faster under the same memory. mvnd -Dmvnd.socketConnectTimeout=300000 -Dmvnd.connectTimeout=300000 -Dmvnd.cancelConnectTimeout=300000 -Dmaven.compile.fork=true -Dmvnd.cache=true -Dmaven.test.skip=true -Dmaven.javadoc.skip=true clean package Question 1: Why is the compilation speed of the daemon process temporarily created in the Jenkins pipeline slow, and why is it destroyed after compilation? Question 2: How should I configure to make the speed of compiling JAR files stable and prevent the daemon process from occupying the container content for a long time? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
