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
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/java-on-azure/benchmarking.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -203,7 +203,7 @@ Each iteration shows how many times per second your `benchmarkHttpResponse()` me
203
203
REMEMBER: The numbers below are just data. To gain reusable insights, you need to follow up on
204
204
why the numbers are the way they are. Use profilers (see -prof, -lprof), design factorial
205
205
experiments, perform baseline and negative tests that provide experimental control, make sure
206
-
the benchmarking environment is safe on JVM/OS/HW level, ask for reviews from the domain experts.
206
+
the benchmarking environment is safe on JVM/OS/HW level, ask for reviews from the domain experts. Do not assume the numbers tell you what you want them to tell.
207
207
208
208
NOTE: Current JVM experimentally supports Compiler Blackholes, and they are in use. Please exercise
209
209
extra caution when trusting the results, look into the generated code to check the benchmark still
0 commit comments