I have tried MrPlow and it seems to work. Only a message on the node appears and I don't know what does it mean. `INFO snowblossom.node.SnowUserService sendNewBlocks Error: io.grpc.StatusRuntimeException: CANCELLED: call already cancelled` Something I have to be worried? It seems every provided share by the miner is causing that message. Thanks
not an issue, just clutters the logs
`creating field: snow/mainnet/snowblossom.7 memfield=true, precache=0` what's the precache thingy, something to sorta 'grep the files' and push them into the fscache, but no hard guarantees they'll stay in there?
hey guys, where does the node store the block files?
it has a db directory you point it at and that'll be either rocksdb or lobstack based on what you configured
Check out mining tuning
it is just a way to load some of the field into memory
ah that thing, was wondering why that's an integer - forgot about that already
the 'windows be gone' ward
@Fireduck is there some inherent architectural choice which would prevent one from tweaking the thread count at run time? i'm thinking about looking at making the miner autotune
nope, thread coutn at runtime is good
so it's some run of the mill thread pool you've gone with and not manual juggle hell?
it's so confusing trying to help people fiddle with the thread counts and/or to try to explain to them why something does or does not work right now for them, it'd be nice if that could just take care of itself
There was a company that made a cake mix. Just add water, mix, bake.
Customers didn't like it, they thought it wasn't real cooking.
So they changed the recipe so that they had to add one egg as well.
So water and egg, mix, bake.
People liked that a lot more.
But yeah, thread autotune would be good to do.
But for now maybe makes people feel involved.
the egg is the `-Xmx`
i suppose it could just check the available heap space and 1) put the whole field in if it fits 2) start putting it in at one (1GB?) chunk at a time, until there's < 2GB heap space left
Yeah, plenty of egg here already
hmm, was it only a suggestion to break the snow fields into chunks? that'd play into that nicely - i remember talk of letting people use multiple drives as otherwise the requirements eventually get expensive
and i suppose that'd also allow for distributed mining, but dunno if the share schemes for pools would overcomplicate
but that's essentially the same bunch of trouble as balance management of electrical grids, so fair systems already exist
Yeah, breaking up the fields is planned
Probably 1gb chunks
Ordered list of sources
Use first source that has chunk
i supposed 1GB is sane for various reasons
I mention it in case you have thoughts on it
Could make them arbitrary but it will be complicated for already confused users
Yeah, just use dd with seek and skip to get the size you want
I can see that going poorly
oh man, that'd be the new `rm -rf /` or 'delete system32' - almost worth it for the marketing-by-meme ensuing
'order your sources by speed' would be also smart then as the miner should offload from the slowest ones
and yet again a simple enough egg
Especially if they can manage a ram fs and put what they can there as first source
mostly currently the field does not actually stay in the fs cache as it's a monolith, so just having it in 1G chunks would help people out a lot
distributed mining looks too hard to be of consideration anytime soon, though: https://www.usenix.org/legacy/event/fast10/tech/full_papers/eshel.pdf
also i think i'm done with deeper systems hacks now, was still considering to make everything `POSIX_FADV_DONTNEED` unless whitelisted, but meh
but for a rough overview: https://github.com/Feh/nocache minimize caching effects
https://github.com/snowblossomcoin/snowblossom/blob/753e0500088d17aa73d5e3b145ebd49b4f0278b3/example/scripts/sample0-build-from-source.sh#L48 Line 48 in </snowblossomcoin/snowblossom/commit/753e0500088d17aa73d5e3b145ebd49b4f0278b3|753e050> systemctl link /var/snowblossom/source/example/systemd/snowblossom-node.service
What should I work on?
hm
[snowblossomcoin/snowblossom] Issue closed by cluelessperson
[snowblossomcoin/snowblossom] Issue closed by cluelessperson