Reducing Go Execution Tracer Overhead with Frame Pointer Unwinding

1. go

   1 2,274 128,440 10.0 Go

   The Go programming language

   

   It was interesting to look directly at the source code linked in the article for stack unwiding [1]. In particular, it's neat to see how thoroughly documented this file is. Reminds me of poking around the SQLite codebase.

   [1] https://github.com/golang/go/blob/6b8b7823c7fd9f3f2317f65712...

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. zap

   2 55 23,223 5.6 Go

   Blazing fast, structured, leveled logging in Go.

   

   Would this speed up capturing stack traces? The use case I have in mind is stack traces for logging. The Zap logger has a mild warning [1] about stack traces being relatively expensive.

   [1]: https://pkg.go.dev/go.uber.org/zap#Stack

Suggest a related project