You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Currently we are using 85% as JVM heap usage limit. If JVM heap usage exceeds 85%, will stop detector. JVM heap usage is not very accurate to evaluate the real system pressure. GC may collect most young generation and system will back to under 85% quickly.
As @kaituo suggested, we can change to old_gen_heap_usage / total_heap > 80% which is more accurate to reflect the memory pressure.
The text was updated successfully, but these errors were encountered:
Currently we are using 85% as JVM heap usage limit. If JVM heap usage exceeds 85%, will stop detector. JVM heap usage is not very accurate to evaluate the real system pressure. GC may collect most young generation and system will back to under 85% quickly.
As @kaituo suggested, we can change to
old_gen_heap_usage / total_heap > 80%
which is more accurate to reflect the memory pressure.The text was updated successfully, but these errors were encountered: