Hi everyone

Sorry for dropping off the grid for several past weeks. I got selected to
talk about Continuous Benchmarking at Fosdem a week ago. Preparing the talk
was a lot of work, and also releasing some software that is mentioned in
the talk, so that it  exits when I talk about it, was even more work. So
I've been a bit in caveman mode since December, but slowly coming back to
normal mode now.

A big part of the talk of course is Change Point Detection. Video and
slides are here if you're interested:
https://blog.nyrkio.com/2026/02/10/continuous-benchmarking-howto-talk-at-fosdem-2026/

In preparing the talk I came to the conclusion that people are gravitating
around the term "Continuous Benchmarking", where I have previously used
"Continuous Performance Engineering". The latter is also used on
otava.apache.org and README, so this is just a "note to self" that at some
point we may want to join the "Continuous Benchmarking" folks.

Important milestone for a movement to at least agree on what it is going to
call itself :-)


I'll start replying to things and reviewing PRs which are waiting for me,
but wanted to send this kind of generic message that I'm alive and feel
free to ping me directly if you want me to focus on some specific PR or
question first.

henrik
-- 
*nyrkio.com <http://nyrkio.com/>* ~ *git blame for performance*

Henrik Ingo, CEO
[email protected]                               LinkedIn:
www.linkedin.com/in/heingo
+358 40 569 7354                                 Twitter: twitter.com/h_ingo

Reply via email to