Skip to content
This repository was archived by the owner on May 26, 2023. It is now read-only.

Conversation

@melvin15may
Copy link

@melvin15may melvin15may commented Apr 21, 2020

  • Update README to add information about corresponding JVM unified logging framework options
  • Update regionsize_vs_objectsize.sh for jvm logging framework

Comment on lines +10 to +14
fit2mb=`grep "source: concurrent humongous allocation" ${log} | sed 's/.*allocation request: \([0-9]*\).*/\1/' | awk '{if($1<1048576) print}' | wc -l`
fit4mb=`grep "source: concurrent humongous allocation" ${log} | sed 's/.*allocation request: \([0-9]*\).*/\1/' | awk '{if($1<2097152) print}' | wc -l`
fit8mb=`grep "source: concurrent humongous allocation" ${log} | sed 's/.*allocation request: \([0-9]*\).*/\1/' | awk '{if($1<4194304) print}' | wc -l`
fit16mb=`grep "source: concurrent humongous allocation" ${log} | sed 's/.*allocation request: \([0-9]*\).*/\1/' | awk '{if($1<8388608) print}' | wc -l`
fit32mb=`grep "source: concurrent humongous allocation" ${log} | sed 's/.*allocation request: \([0-9]*\).*/\1/' | awk '{if($1<16777216) print}' | wc -l`
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is slight difference between log lines of legacy GC options and jvm unified logging event

Legacy

 0.106: [G1Ergonomics (Concurrent Cycles) request concurrent cycle initiation, reason: occupancy higher than threshold, occupancy: 60817408 bytes, allocation request: 1048592 bytes, threshold: 60397965 bytes (45.00 %), source: concurrent humongous allocation]

Unified Framework

[334133.389s][debug][gc,ergo,ihop  ] Request concurrent cycle initiation (occupancy higher than threshold) occupancy: 390070272B allocation request: 524304B threshold: 350322636B (32.63) source: concurrent humongous allocation

@melvin15may melvin15may changed the title Add disclaimer for JVM unified logging framework Add alternative opt for JVM unified logging framework and update regionsize_vs_objectsize Apr 21, 2020
-XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCApplicationStoppedTime -XX:+PrintAdaptiveSizePolicy
```
_For JVM Unified Logging Framework, corresponding options can be found [here](https://docs.oracle.com/javase/9/tools/java.htm#JSWOR-GUID-9569449C-525F-4474-972C-4C1F63D5C357).
For example, for legacy GC flag `-XX:PrintAdaptiveSizePolicy` (used to add log lines to calculate humongous objects with `regionsize_vs_objectsize.sh`) instead use `-Xlog:ergo*=debug`._
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-XX:PrintAdaptiveSizePolicy is missing a +: -XX:+PrintAdaptiveSizePolicy

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants