Oracle SOA(EAI) G1GC
- 공유 링크 만들기
- X
- 이메일
- 기타 앱
<Environment>
■ SOA Version : Oracle Cloud SOACS 12.2.1.4 (Market Place)
■ java version 1.8.0_261
■ Java Memory Garbage Collection Type : G1GC
-----------------------------------------------------------------------------------------------------
In this post, I will compare between Parallel GC and G1 GC for Oracle SOA(EAI).
For this, you need to know something as bellow..
EAI
- Enterprise Architecture Integration
What is Java Memory Garbage Collection (GC)?
- Memory management
- Delete unused memory automatically
Java Memory Garbage Collection Types
- - Serial Garbage Collector
- - Parallel Garbage Collector -> Default GC below 1.9
- - CMS Garbage Collector
- - G1(Garbage First) Garbage Collector -> Default GC above 1.9
Parallel Garbage Collector Logic
Shortly,
Memory usage follow...
from Young Generations [Eden -> Survivor 0 / Survivor 1] to Old Generations.
Please refer to following jvisualvm capture.
Finally, all of usage memory will be full in Old Generation,
and then,
Major GC will work !!
-> If memory size is so big, it takes long time(s) for Major GC.
Shortly, there are no memory usage follow as Parallel GC.
G1GC use all Generation automatically and delete unused(garbage) memory
Please refer to following jvisualvm capture.
As above GC part(Red Box), G1GC delete unused(garbage) memory in short time(ms).
Well, GC can be many of times but they are very short.
[G1GC could take long time for GC because of big interface data, but I think interface data should be light]
In my opinion, SOA(EAI) should transport data in real time.
So, GC time(Stop the World) should be short as G1GC.
And, I think that we do not need to wait for major GC.
Just change JAVA parameter option.
-XX:+UseParallelGC to -XX:+UseG1GC
[There are a lot of options, but I do not use that]
Many thanks~~~:)
- 공유 링크 만들기
- X
- 이메일
- 기타 앱