fox.cpp c4ea9a730f Instrument the SMTP code using runtime/trace ... runtime/trace together with 'go tool trace' provides extremely powerful tooling for performance (latency) analysis. Since maddy prides itself on being "optimized for concurrency", it is a good idea to actually live up to this promise. Closes #144. No need to reinvent the wheel. The original issue proposed a solution to use in production to detect "performance anomalies", it is possible to use runtime/trace in production too, but the corresponding flag to enable profiler endpoint is hidden behind the 'debugflags' build tag at the moment. For SMTP code, the basic latency information can be obtained from regular logs since they include timestamps with millisecond granularity. After the issue is apparent, it is possible to deploy the server executable compiled with tracing support and obtain more information ... Also add missing context.Context arguments to smtpconn.C.		2019-12-13 17:31:35 +03:00
..
smtpconn.go	Instrument the SMTP code using runtime/trace	2019-12-13 17:31:35 +03:00
smtpconn_test.go	Move most code from the repo root into subdirectories	2019-12-06 01:35:12 +03:00
smtputf8_test.go	Instrument the SMTP code using runtime/trace	2019-12-13 17:31:35 +03:00