Profile and Optimize a Hot-Path Tokenizer in Go
by Jesús Espino
VictoriaTraces splits every span it ingests into tokens, and that tokenizer sits right on the hot path of ingestion. Build a benchmark for it, take a CPU profile from that benchmark, and work out where the time actually goes and why - then fix it, and see how much of the improvement still holds up once the rest of the indexing work is put back around it.

