Full-codebase-audit 2026-05-30 outputs: - Audit report: 09 - Audits/Full Codebase Audit - 2026-05-30.md - 81 issue files ISSUE-055..135 (decisions + 1 skipped no-brainer). - Scanner docs from scratch (was zero): architecture, data model, API ref, payment flow, operations runbook + repo README. - Doc-sync updates across API reference, data models, flows, design system. - Secret Rotation Runbook (08 - Operations) for the exposed credentials. - Reusable workflow guide (07 - Development) + .claude/workflows/full-codebase-audit.js. Issues remain status:open intentionally — the code fixes are uncommitted-then-committed working-tree changes per repo and aren't "resolved" until merged/deployed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
40 lines
1.1 KiB
Markdown
40 lines
1.1 KiB
Markdown
---
|
|
issue: 131
|
|
title: "Scanner: Tron/TON workers don't share HTTP transport — no connection reuse"
|
|
severity: low
|
|
domain: Scanner
|
|
labels: [performance, scanner]
|
|
status: open
|
|
created: 2026-05-30
|
|
source: Full Codebase Audit 2026-05-30
|
|
---
|
|
|
|
# Scanner: Tron/TON workers don't share HTTP transport — no connection reuse
|
|
|
|
**Severity:** low
|
|
**Domain:** Scanner
|
|
**Labels:** performance, scanner
|
|
|
|
## Description
|
|
|
|
`scanner/tron_chain.go:38` creates separate `http.Client` instances per worker without a shared `http.Transport`. This means TCP connections to the same host are not reused across workers, increasing latency and connection overhead.
|
|
|
|
## Options
|
|
|
|
1. Use a shared `http.Client`/`Transport` with `MaxIdleConnsPerHost` set.
|
|
2. Per-worker clients but with explicit transport tuning.
|
|
3. Leave as-is.
|
|
|
|
## Recommendation
|
|
|
|
Share a single tuned transport across workers for connection reuse.
|
|
|
|
## Affected Files
|
|
|
|
- `scanner/tron_chain.go:38`
|
|
- `scanner/ton_chain.go` — similar pattern
|
|
|
|
## References
|
|
|
|
- [Full Codebase Audit 2026-05-30](../09%20-%20Audits/Full%20Codebase%20Audit%20-%202026-05-30.md) — DEC-70
|