Shulou(Shulou.com)06/02 Report--

This article mainly explains the "springboot project compilation, operation optimization how to operate", the article explains the content is simple and clear, easy to learn and understand, the following please follow the editor's ideas slowly in-depth, together to study and learn "springboot project compilation, operation optimization how to operate" it!

This blog mainly records the related actions of bloggers when using springboot:

(1) compile, package and execute the springboot project

Local: mvn clean package-U-- settings D:\ devsoft\ apache-maven-3.5.3\ conf\ huxs1settings.xml-Dmaven.test.skip=true-Pdev

Server: mvn clean package-U-Dmaven.test.skip=true-Ptest

(2) run the springboot project

Java-jar xxx.jar

/ / start the springboot project by pinpoint-agent monitoring

Nohup java-Xms6144m-Xmx6144m-XX:PermSize=1024m-XX:MaxPermSize=1024m-javaagent:/home/xpp/apm/pinpoint-agent/pinpoint-bootstrap.jar-Dpinpoint.agentId=PP_123.xx.xx.115-Dpinpoint.applicationName=crs_bb_bb-xxx-data-jar xxx.jar

(3) SpringBoot enables remote debug and remote monitoring

a. Turn on remote debug

Nohup java-Xdebug-Xrunjdwp:server=y,transport=dt_socket,address=3286,suspend=n-jar wtp-service-pay-0.0.1-SNAPSHOT.jar-- spring.profiles.active=test > wtp-service-pay.log 2 > & 1 &

b. Enable jvisualVM remote monitoring

Nohup java\

-Djava.rmi.server.hostname=12x.xx.xx.112\

-Dcom.sun.management.jmxremote\

-Dcom.sun.management.jmxremote.port=9999\

-Dcom.sun.management.jmxremote.authenticate=false\

-Dcom.sun.management.jmxremote.ssl=false\

-Dcom.sun.management.jmxremote.rmi.port=9999\

-jar wtp-service-pay-0.0.1-SNAPSHOT.jar-- spring.profiles.active=test > wtp-service-pay.log 2 > &

/ / you can also use the

Org.jolokia

Jolokia-core

(4) production tuning (8G memory, 64-bit linux,JDK1.8)-- pressure test tuning result

Nohup java\

-Xms6144m-Xmx6144m-Xmn2048M-XX:OldSize=4096M-Xss1024k\

-XX:MetaspaceSize=128m-XX:MaxMetaspaceSize=256m\

-XX:+UseConcMarkSweepGC\

-XX:+UseParNewGC\

-XX:+UseCMSCompactAtFullCollection\

-XX:CMSFullGCsBeforeCompaction=10\

-XX:+CMSClassUnloadingEnabled\

-XX:+CMSParallelRemarkEnabled\

-XX:+UseCMSInitiatingOccupancyOnly\

-XX:CMSInitiatingOccupancyFraction=70\

-Djava.rmi.server.hostname=12x.xx.xx.112\

-Dcom.sun.management.jmxremote\

-Dcom.sun.management.jmxremote.port=9999\

-Dcom.sun.management.jmxremote.authenticate=false\

-Dcom.sun.management.jmxremote.ssl=false\

-Dcom.sun.management.jmxremote.rmi.port=9999\

-Xdebug-Xrunjdwp:server=y,transport=dt_socket,address=121.xx.xx.112: 8000 spring.profiles.active=test-jar $JAR_NAME-- spring.profiles.active=test > / home/app/logs/xxxxsearch-catli.out 2 > & 1 &

Finally, about JVM:

-XX:PermSize=1024M permanent generation size

-XX:MaxPermSize=1024M-Xms4096M-Xmx4096M MaxPermSize is the maximum permanent generation size

-Xmn1024M-XX:SurvivorRatio=8

-XX:+DisableExplicitGC shutdown program initiatively calls gc

-XX:+UseConcMarkSweepGC

-XX:+UseParNewGC

-whether to clean up the memory after XX:+UseCMSCompactAtFullCollection full garbage collection

-XX:CMSFullGCsBeforeCompaction=10 how many times full garbage collection and after a memory consolidation

-whether XX:+CMSClassUnloadingEnabled allows (permanent generation) cleanup

-XX:+CMSParallelRemarkEnabled lower mark pause

-XX:+UseCMSInitiatingOccupancyOnly-XX:+UseCMSInitiatingOccupancyOnly specifies that HotSpot VM always uses the value of-XX:CMSInitiatingOccupancyFraction as the space usage limit for old to start CMS garbage collection. If you don't use-XX:+UseCMSInitiatingOccupancyOnly, HotSpot VM simply uses this value to start the first CMS garbage collection, followed by values automatically calculated using HotSpot VM.

The value of-XX:CMSInitiatingOccupancyFraction=70 specifies what the space occupancy rate of the Old generation should be when CMS garbage is collected. For example, if you want to start CMS garbage collection when the old occupancy rate is 65%, you can set-XX:CMSInitiatingOccupancyFraction=65.

-XX:TargetSurvivorRatio=90 sets the target utilization of the survivor zone. The default is 50, that is, the target utilization rate of objects in the Portugal area is 50%.

-the maximum XX:MaxTenuringThreshold=20 promotion age threshold, which defaults to 15. If the object survives after the number of times it has survived (the number of times it has passed the YGC) in the new generation, it will be promoted to the old age. After each YGC, the age plus 1, when the age of the object in the survivor area reaches TenuringThreshold, it indicates that the object is an immortal object and will be directly promoted to the old age.

(5) Monitoring commands in tuning (to be continued here)

a. Command line: jps, jstat, jinfo, jmap, jhat, jstack

B.jdk tools (bin catalog): jvisualvm.exe, jconsole.exe

(6) Summary of common configurations

Heap settings

-Xms: initial heap size

-Xmx: maximum heap size

-XX:NewSize=n: sets the size of the younger generation

-XX:NewRatio=n: sets the ratio of the younger generation to the older generation. For example, 3 means that the ratio of the young generation to the old generation is 1:3, and the young generation accounts for 1% of the sum of the young generation and the old generation.

-XX:SurvivorRatio=n: the ratio of Eden region to two Survivor regions in the young generation. Notice that there are two in the Survivor area. For example: 3, which means Eden:Survivor=3:2, and one Survivor area accounts for 1x5 of the whole younger generation.

-XX:MaxPermSize=n: sets the persistent generation size

Collector Settings

-XX:+UseSerialGC: set the serial collector

-XX:+UseParallelGC: sets the parallel collector

-XX:+UseParalledlOldGC: set parallel older generation collectors

-XX:+UseConcMarkSweepGC: sets the concurrent collector

Garbage collection statistics

-XX:+PrintGC

-XX:+PrintGCDetails

-XX:+PrintGCTimeStamps

-Xloggc:filename

Parallel Collector Settings

-XX:ParallelGCThreads=n: sets the number of CPU to use when collecting by the parallel collector. Number of threads collected in parallel.

-XX:MaxGCPauseMillis=n: sets the maximum pause time for parallel collection

-XX:GCTimeRatio=n: sets the percentage of garbage collection time to program running time. The formula is 1 / (1cm n)

Concurrent Collector Settings

-XX:+CMSIncrementalMode: set to incremental mode. It is suitable for single CPU situation.

-XX:ParallelGCThreads=n: the number of CPU used when the young generation of the concurrent collector is collected in parallel. Number of parallel collection threads

Thank you for your reading, the above is the "springboot project compilation, operation optimization how to operate" content, after the study of this article, I believe you on the springboot project compilation, operation optimization how to operate this problem has a deeper understanding, the specific use of the situation also needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.