Talk proposal: Breaking and optimizing the Prometheus parser

Open Maniktherana opened this issue 4 months ago • 5 comments

Breaking and optimizing the Prometheus parser

Hi I'm Manik, Prometheus Contributor

I tried to contribute to Prometheus, but it was complex and had a lot of moving parts. It took me a month before I could open my first PR
Now I'm optimizing (by 250+%!) the OpenMetrics Parser (a mess I made in the first place)
I'll talk about how Prometheus uses Lex to eventually create a high performance parser.
I'll cover techniques to navigate complex codebases that helped me become a confident contributor
Finally I get into Benchmarking go with the stdlib & benchstat. Possibly covering load testing my work with K6 & showing off flamegraphs

I've navigated large frontend codebases and rest apis with ease, but Prometheus turned out to be a different beast
Eventually I learned how to harness a debugger and how to find what im looking for through rigorous testing

Prometheus uses Lex which is wrapped by a Parser
I cover how this works and why its needed
I go over what I worked on and why its used wayyyy too much memory and how I go about optimizing it by over 300%

Cover microbenchmarking, macrobenchmarking and considerations for both
A little bit about load testing
All this comes together to help identify perfomance bottlenecks and eventually help you optimize your mess of a codebase

Relevant stuff I cover:

10min

No response

Primary a web developer Dabbling with Go and contributing to Prometheus

19/10/2024

My work is about what I did in Go but the techniques I cover should be language agnostic I'll try to keep it as approachble as possible

I'm strapped for availability so the description I gave is for a longer talk (30-40min) but the scope for this one is much smaller

Oct 12 '24 15:10 Maniktherana