Oct 10, 2025

....compiling! let you know

it seemed it didn't compiled it

this is how I pass compiler flags reliably

Thanks @eynhaender! Checking the log it seems that it does those flags everywhere exept to libbitcoin-system"

will try with this more manual options

-msha is shani right?

unfortunately I don't have avx512

yes. and of course you need to adapt the options for your specific hardware. -mavx2 will add axv2

With the cmake installer and cmake in general, arguments at the configuration level are written -Denable-shani

@pmienk it's strange the usual script does not work... if you want I can provide the log in DM

this matches the convention of that platform. configure.ac is an autotools artifact. passing the cflags directly without signaling to our build system will not fully inform the compilation as far as I'm aware as it fails to define WITH_SHANI which was relied upon to enable the codepaths

@parsevalbtc Happy to look at your parameterization.

Eventually built with cmake recipe. Is fast like a rocket with the optimizations compiled and ssd disk 🚀🚀🚀

.... unfortunately it will hit disk space

in less than 40 I'm about at 500k bloks

CPU at 50% with network download ~120 MiB/s

hit disk limit

Was that 100% of network capacity?

yes

Well, that's as good as we can do 🙂

just below 1 Gbps

Nice, ubuntu?

debian 13

Now I am moving the bitcoin folder to an external disk

I expect degradation of performances.... but let's see

yes

This pc in 16GB RAM, but the (internal) disk is super fast

It will start getting slower as the chain grows, because of the limited RAM. You only got to about 25% chain.

25% in space right?

space and txs (and inputs/outputs).

in a past dev meeting you mentioned that at least you have to store the table's head in the RAM. Actually I don't remember how big those are...

the question is, if the RAM size is below heads' size, the node put's them between RAM and disk or only to the disk?

~16GB (without address index)

or is the OS which chose how to split them?

It's all in RAM, but these are frequently and randomly accessed during writes. The tables are not, mostly append.

you mean table's heads are always loaded in RAM (and eventually swap for the exceeding part)?

All of the files are always loaded into RAM and swapped as necessary.

With external disk,as expected, is running significantly slower, but it is not stalling. So keep you posted!