mirror of
https://github.com/luxfi/node.git
synced 2026-10-30 15:24:05 +00:00
zeekay
7cf87b230b
The module already called itself github.com/luxfi/node while containing no node in Go: cmd/luxd was twenty-one lines that printed the size of a few types, and the Go column of the matrix measured a VM plugin. A repo that fetches the thing it claims to be has not replaced it, so the Go sources move in — 1515 files, the daemon and everything under it — and the build reaches outside this module for nothing. Rust and C++ sit beside it unchanged and are still measured against it by the differential. That is the point of one repo: the reference implementation and the two ports are the same checkout, so parity is a thing you can run rather than a thing you assert. Verified: builds, and the closure carries no lux-private — checked at build time rather than believed. The daemon starts twelve chains on a local network (P X C Q Z A B G K M F, plus D through its plugin) and reports healthy.
32 lines
893 B
JSON
32 lines
893 B
JSON
{
|
|
"_comment": "Max memory profile for production/high-performance. Target: ~512MB per node",
|
|
"_targets": {
|
|
"memory_per_node": "512MB"
|
|
},
|
|
|
|
"db-cache-size": 67108864,
|
|
"db-memtable-size": 67108864,
|
|
"state-cache-size": 268435456,
|
|
"block-cache-size": 134217728,
|
|
|
|
"network-peer-read-buffer-size": 16384,
|
|
"network-peer-write-buffer-size": 16384,
|
|
|
|
"throttler-inbound-at-large-alloc-size": 16777216,
|
|
"throttler-inbound-validator-alloc-size": 16777216,
|
|
"throttler-inbound-node-max-at-large-bytes": 8388608,
|
|
"throttler-inbound-bandwidth-max-burst-size": 8388608,
|
|
|
|
"throttler-outbound-at-large-alloc-size": 16777216,
|
|
"throttler-outbound-validator-alloc-size": 16777216,
|
|
"throttler-outbound-node-max-at-large-bytes": 8388608,
|
|
|
|
"consensus-app-concurrency": 4,
|
|
|
|
"log-level": "info",
|
|
"log-rotater-max-size": 100,
|
|
"log-rotater-max-files": 10,
|
|
|
|
"fd-limit": 65536
|
|
}
|