Oct 27, 2026

you're not maxing anything?

that's pretty low for ram usage given where we were a year ago

It's full validation, with download and validation and signature collection and flushing and gpu validation all in balance.

it's close to max network, gpu is free, disk flushing is just keeping ram under control, not costly, and cpu is just getting block/prevout data, collecting sigs and running the light scripts.

it's almost network paced validation.

so 2.5 spread across two nics that are pulling 1.1gbps and 944mbps? was wondering

it varies, but peak on these networks is 2.3 per side. milestone can pull a nearly sustained 4.6.

but we've never maintained download rates much above zero when validating.

the node would alternate between download waves and CPU waves, with gpu mixed in.

What's happening here is I'm looking up prevouts through the very costly input point (tx hash:index) natural key hashmap search, to populate prevouts, while downloading. and associating those to their output through an association table, which then allows me to drop the hashmap association - which works in concurrency window batches. drops 100GB from the store, and makes it possible to run much more confirmation while downloading, since it becomes low cost query.

disk is low, ram is low, cpu is modest, and gpu is yawning, but the pace is hot... validating (see gpu spikes) while also downloading at 4Gbps.

on track for any new records?

hit one earlier, but really working all day to get this to fit into our 8/16GB min profiles.

I just decided to try a run for fun on shelly, and the small box work has made this so much leaner.

It's a tie for the record, at 52 mins full validation on Shelly.

Resource consumption down about 14%, which should show some payoff on the minis.