lmao, I feel like most devs don't have sysadmin experience and it shows
Discussion
please tell me, sysadmin knowledge for dev might be alike know the "____" for experience in real estate building ?
for example, the foundations?
I would call in-depth knowledge of computer hardware as the foundation analog. I don't know that I have a good analog to sysadmin. Its deploying and using your own product on your own hardware, following practices you'd expect other enterprises to follow.
alright then I could translate that to my trench as the very forging of habitat, more precisely its conception. a sysadmin thus conceives not only the final use of the product as well he does so for the forms and ways
i don't have a lot, never done it professionally, nearly got my Network+ back in 2016, been using unix shells since 1995 and i can write adequate scripts and dockerfiles
as a dev, i'm very interested in the structural limits of hardware though... when i was a kid i saw too many amiga demos and what those crazies could do left a big stamp on me
like, on the subject of disks, i know that badger has configurations that can reduce the rate of flushing the log and compactions, and kernels can be tweaked to delay flushing the cache to disk for this, but eventually it does have to get written
and regarding bitcoin-core and indeed btcd, their database implementations leave a lot to be desired (and they are both running ancient leveldb) and all the hype about strfry when it is basically using leveldb *with bonus memory mapped storage* it is so horribly yawn to me i can't stand it
since 2016 there has been the Wisckey paper that demonstrated that splitting key/value stores into two separate logs drastically reduced the amount of disk writes required and make it so you could engineer databases to make more use of the key fields, which are preferentially kept in memory and flushed infrequently, and this leads to dgraph, which as far as i know is the best performing graph database
i did mean to build a badger driver back in 2019 for btcd but i never got around to it... but btcd's performance is so abysmal i would never use it for production, and that's the default for LND, which to me just reinforces your point - most devs have little to no understanding of the hardware they are writing code to run on
I don't but my dad is a network engineer and my husband is an electrical engineer and used to be a sys admin. That's why we have all these old electronics. 😂 Probably why I'm so interested in relays.
I told him I need a terabyte for a full BTC node and he was like
for full nodes i highly recommend mini pc's
they don't need to be very performant, 4gb is enough even, just the disk needs to be decently fast and big - most of the data processing happens in one thread by necessity of the way the chain structure works
it's been a while since it was remotely practical to use a HDD, though probably a loud screaming 10k RPM 5.25 might almost do it
but for basics, just a 2.5" SATA SSD and a second one to dump the chain onto once in a while so if it has a failure like nostr:nprofile1qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcpzdmhxue69uhhqatjwpkx2urpvuhx2ue0qy2hwumn8ghj7mn0wd68ytn00p68ytnyv4mz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcqyqpk2v724perw62x6nj0m6jvrgzyrmdr3j3dnk2p0wekqpkt42l4s3v0jrr is talking about you don't have to wait forever to have it come back online
We have a NAS, but he doesn't want me messing with it. 🙄
anything less than a 10Gbit network connection to the disk is not gonna be much fun, 5Gbit is adequate
My cluster gets by with a 4gig lacp across 3 nodes, haven't really noticed any performance degradation for what I do. I guess caches make the most of it.
people say cln doesn't support pruned nodes but that could just be boogle not letting us search for stuff in the last 5 years cause it seems like both cln and lnd support pruned nodes. a lightning head would know more i can vouch for lnd at least, and litd. ⚡
The only way I got cln to work was with a full node. I think there is a way to prune it after a while, but if I already need 600gb of space to get is started I guess Ill just keep it. When cln starts up it requests genesis block forward and if it's not there it fails and logs an errors something like "missing block data, cln doesn't support pruned nodes"
My old laptop only had 2GB of RAM. 😂 Wimpier than a π
You need a 2TB lol
Leave me alone to grieve. 😭
nope
You can run a pruned node with less.
A full node is already 1TB with electrum.
A full node with fulcrum needs 2TB going forward.
is fulcrum something CATman is talking about?
Fulcrum is an electrum server that does rapid indexing, which is great for deep wallets.
can't be very rapid if it uses 1400Gb of space
It doesn't. A full node with electrum is currently 1TB. A full node with fulcrum is over 1TB now. So a 2TB SSD is a good idea for long term future use ( epsecially if you want to use a faster lookup like fulcrum ) so you don't have to download a ibd again.
i just use xrdp and directly use the bitcoin core GUI, and the only thing i imagine happening next might be running CLN on it
but the chain does grow like 100mb/day so 10 days = 1 gb and 350 left so 3500 days... ok, hah my node will be good until the hardware fails probably - and yes i have address and tx indexes enabled, uses 680gb
my mini pc was 140 euros and has 8gb memory so it's overkill hardware really, i just envisioned maybe i might run LN and one or two other things on it, i had imageproxy running on it for a while