changeset 54506:274361bd6915

8220228: Improve Shenandoah pacing histogram message Reviewed-by: rkennke
author shade
date Thu, 07 Mar 2019 10:22:19 +0100
parents a7cccbdf73f3
children 0f9a54a13803
files src/hotspot/share/gc/shenandoah/shenandoahPacer.cpp
diffstat 1 files changed, 5 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/src/hotspot/share/gc/shenandoah/shenandoahPacer.cpp	Wed Mar 06 16:01:01 2019 +0100
+++ b/src/hotspot/share/gc/shenandoah/shenandoahPacer.cpp	Thu Mar 07 10:22:19 2019 +0100
@@ -299,4 +299,9 @@
   }
   out->print_cr("%23s: " SIZE_FORMAT_W(12) SIZE_FORMAT_W(12) " ms", "Total", total_count, total_sum);
   out->cr();
+  out->print_cr("Pacing delays are measured from entering the pacing code till exiting it. Therefore,");
+  out->print_cr("observed pacing delays may be higher than the threshold when paced thread spent more");
+  out->print_cr("time in the pacing code. It usually happens when thread is de-scheduled while paced,");
+  out->print_cr("OS takes longer to unblock the thread, or JVM experiences an STW pause.");
+  out->cr();
 }