GitHub Actions run
Wall Time
9 days ago 8f9d0d3 development pull_requestUnknown Walltime execution environment detected
Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data. For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.Compare
Suggested base runs: •
15 total
BenchmarkMutexOperations
services/backend-api/test/benchmark/benchmark_test.go25 ns
BenchmarkTruncateSQL
services/backend-api/internal/database/telemetry_test.go49 ns
BenchmarkEncrypt
services/backend-api/internal/crypto/encryption_test.go655 ns
BenchmarkSafeLog
services/backend-api/internal/utils/masking_test.go43.7 µs
BenchmarkErrorHandling
services/backend-api/test/benchmark/benchmark_test.go125 ns
BenchmarkMaskString
services/backend-api/internal/utils/masking_test.go98 ns
BenchmarkDecrypt
services/backend-api/internal/crypto/encryption_test.go547 ns
BenchmarkConcurrentRequests
services/backend-api/test/benchmark/benchmark_test.go269.6 µs
BenchmarkMiddleware
services/backend-api/test/benchmark/benchmark_test.go2.2 µs
BenchmarkParseSQL
services/backend-api/internal/database/telemetry_test.go1.2 µs
BenchmarkTimeOperations
services/backend-api/test/benchmark/benchmark_test.go212 ns
BenchmarkContextOperations
services/backend-api/test/benchmark/benchmark_test.go223 ns
BenchmarkChannelOperations
services/backend-api/test/benchmark/benchmark_test.go1.7 µs
BenchmarkAPIPerformance
services/backend-api/test/benchmark/benchmark_test.go12.6 µs
BenchmarkJSONHandling
services/backend-api/test/benchmark/benchmark_test.go5.6 µs