---
title: "Discussion on \"JVM timing options\" | Hashnode"
description: "Discussion on \"JVM timing options\". For as long as I have been coding in Java, we have had requirements to measure the execution time of blocks of code. While the current good practice is to use OpenTelemetry's traces, not every company"
url: "https://hashnode.com/posts/jvm-timing-options/69a00c5baa2899392714153e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [JVM timing options](https://frankel.hashnode.dev/jvm-timing-options?utm_source=hashnode&utm_medium=feed)

For as long as I have been coding in Java, we have had requirements to measure the execution time of blocks of code. While the current good practice is to use OpenTelemetry's traces, not every company

Feb 26 · 4 min read · frankel.hashnode.dev  
Read the article

-   [#java](https://hashnode.com/tag/java)
-   [#timer](https://hashnode.com/tag/timer)
-   [#stopwatch](https://hashnode.com/tag/stopwatch)

## Written by

[Nicolas Fränkel](https://hashnode.com/@nfrankel)

@nfrankel · Geneva

  
[View profile](https://hashnode.com/@nfrankel)

Developer Advocate

Technologist focusing on cloud-native technologies, DevOps, CI/CD pipelines, and system observability. His focus revolves around creating technical content, delivering talks, and engaging with developer communities to promote the adoption of modern software practices. With a strong background in software, he has worked extensively with the JVM, applying his expertise across various industries. In addition to his technical work, he is the author of several books and regularly shares insights through his blog and open-source contributions.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
