zeekayandHanzo Dev 84a4bdf91e perf(indexer): bound the swap history one valuation pass reads ...

The previous commit stopped the pass WRITING a row per swap. It still READ
every swap row in the table, every 30 seconds, into a map.

That is the same shape of mistake one layer down. A live chain's swap table
grows without limit — the Lux C-Chain's already spans blocks 53..1,096,496 in
a 732 MB store — so the cost of a pass grows with chain age forever, and the
allocation churn lands on a process sharing 4Gi with six other chains.

storage.SwapsRaw is replaced by RecentSwapsRaw(limit), which uses the indexed
timestamp column to take the newest `limit` rows in SQL rather than filtering
in Go. The pass takes the newest 50,000.

Where that bound binds, the volume figure is the volume of those 50,000 trades
and the log line says so outright. A partial sum silently presented as a total
is worse than a smaller number that is honest about its window.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-26 18:42:27 -07:00

..

replicate.go

Initial commit: Lux Graph Engine

2026-04-11 13:47:05 -07:00

store_memory.go

perf(indexer): bound the swap history one valuation pass reads

2026-07-26 18:42:27 -07:00

store_sqlite.go

perf(indexer): bound the swap history one valuation pass reads

2026-07-26 18:42:27 -07:00

store_test.go

Add CI/CD pipelines, unit tests, release workflow

2026-04-11 14:25:57 -07:00

store.go

Initial commit: Lux Graph Engine

2026-04-11 13:47:05 -07:00