Skip to main content

The performance impact of auto-instrumentation

UD2.120 (Chavanne) | Day 2 | 11:10 - 11:40 | Speakers: James Belchamber

The performance impact of auto-instrumentation
A picture of a devroom at FOSDEM 2024
Open in browser

Notes

Abstract

Auto-instrumentation sounds like a free lunch - press buttons, get signals - but nothing is truly free. Auto-instrumentation requires resources just like any other process, and this requirement scales with the application it's automatically instrumenting.

So what's the cost? Well, I can't tell you what it will be in your application, but over the last year or so we’ve been auto-instrumenting quite a lot of code. So let's explore some performance testing experiments to learn more about how much you're paying for that free lunch.

Oh, and what are the benefits? Let me show you that too :)

Attachments

Speakers

James Belchamber

Notice: The placeholder video image is licensed under CC BY-SA 4.0. The original image can be found hereChanges made to the image are: Cropped the image to a new ratio, part of the image was cut off.