# \#instrumentation

**URL:** https://discuss.ocaml.org/tag/instrumentation/133.md

[Latest](https://discuss.ocaml.org/latest.md) · [Categories](https://discuss.ocaml.org/categories.md) · [Tags](https://discuss.ocaml.org/tags.md)

---

## [Excluding the runtime from performance measurements](https://discuss.ocaml.org/t/excluding-the-runtime-from-performance-measurements/13637)

<div class="topic-metadata">

**Author:** [@rlepigre](https://discuss.ocaml.org/u/rlepigre)\
**Replies:** 0\
**Last updated:** [December 14, 2023, 1:30pm UTC](https://discuss.ocaml.org/t/excluding-the-runtime-from-performance-measurements/13637 "2023-12-14T13:30:47Z")

</div>

As a bit of context, I recently added instruction counting support to Coq using the Linux perf API, and then starting playing around with a tool to visualize the impact of changes (e.g., to Coq or to Coq plugins) on the …

---

## [Instrumentation?](https://discuss.ocaml.org/t/instrumentation/1188)

<div class="topic-metadata">

**Author:** [@yoriyuki](https://discuss.ocaml.org/u/yoriyuki)\
**Replies:** 4\
**Last updated:** [November 24, 2017, 6:50pm UTC](https://discuss.ocaml.org/t/instrumentation/1188 "2017-11-24T18:50:19Z")

</div>

I’m curious about a way for instrumentation of OCaml code. By instrumentation, I mean taking a complete or partial log of an ocaml code which shows when, what function (or a piece of code) is called with what arguments …