unkinben 45d6cdbc64 perf: batch access-log writes instead of goroutine+insert per request (#91) ...

Fixes #76

## Why
Every proxied request spawned a goroutine running a 5s-timeout single-row INSERT. Under load this is unbounded goroutines and connection-pool pressure.

## Changes
- Add `database.AccessLogEntry` + `InsertAccessLogBatch` (bulk `COPY`).
- The engine starts one background writer that drains a buffered channel and flushes every 128 entries or 2s.
- `logAccess` is now a non-blocking channel send (drops on full buffer), so the request path never blocks on the DB. Best-effort telemetry: a small tail may be lost on abrupt shutdown.

## Validation
- `make e2e` passes.

Reviewed-on: #91
Co-authored-by: Ben Vincent <ben@unkin.net>
Co-committed-by: Ben Vincent <ben@unkin.net>

2026-07-02 22:07:56 +10:00

..

circuit_test.go

Feat/v3 go rewrite (#47)

2026-06-07 19:30:35 +10:00

circuit.go

Feat/v3 go rewrite (#47)

2026-06-07 19:30:35 +10:00

classifier_test.go

Feat/v3 go rewrite (#47)

2026-06-07 19:30:35 +10:00

classifier.go

perf: compile remote match patterns once instead of per-request (#88)

2026-07-02 20:20:00 +10:00

engine.go

perf: batch access-log writes instead of goroutine+insert per request (#91)

2026-07-02 22:07:56 +10:00