mine: hash on every core instead of one (#52)

Satoshi left a note above ThreadBitcoinMiner in 2009:

    //// todo: start one thread per processor,
    ////       use getenv("NUMBER_OF_PROCESSORS")

Nobody did, and it stopped being a nicety when the proof of work
became RandomX. SHA-256d on a 2009 desktop lost little to a
single thread. RandomX is built to be fed by every core at once,
so one thread on a 32-core machine mines at a thirty-second of
what the box can do -- and the only outward sign is a CPU that
looks suspiciously idle. A user reported exactly that: 30 minutes
of "Mining", no blocks, Bitflash sitting at 3.3% CPU while the
2 GB dataset was allocated and fast mode was active. Nothing was
broken. It was hashing on one core.

  bitflash -gen                     # every core but one
  bitflash -gen -genproclimit=8     # exactly eight

Automatic leaves one core to the rest of the node -- accepting
blocks, talking to peers, drawing the window -- because a node
that mines beautifully while falling behind the chain has won
nothing. /genproclimit overrides it, and a count several times
the core count is refused rather than quietly thrashing.

The wrapper was already built for this: RandomXCreateMinerVM says
"own VM, not shared", and the ~2 GB dataset is one allocation
every thread reads. Only the 2 MB scratchpad multiplies, so
sixteen threads cost about 32 MB more than one. The startup line
says so, because "why is it using 2 GB" is the first question
anyone asks.

Two things had to be right for this to be safe:

  - Shutdown. Miners share slot 3 of vfThreadRunning and StopNode
    waits for every slot before DBFlush tears the database down.
    With several, the first one out announced that everyone had
    finished while the rest were still calling ProcessBlock, so
    they are counted now and only the last one clears the flag.
    The three CheckForShutdown(3) calls inside the miner became
    plain returns: _endthread() does not unwind on Windows, so
    the bookkeeping would have been skipped there.

  - Duplicated work. Each thread makes its own key, and the
    coinbase pays it, so every thread has a different merkle root
    and searches a different space. Block assembly was already
    under cs_main and cs_mapTransactions; AddKey and ProcessBlock
    take their own locks.

Verified on both platforms: four distinct thread ids reach the
hashing loop and all report back on shutdown, which exits 0 with
DBFlush running. Auto picks cores-1 (1 on a 2-core box, correctly
reported). Speedup itself needs a many-core machine to show and
has not been measured here -- the claim in this message is about
threads doing work, not a benchmark.

Not touched: RandomX's memory. RANDOMX_DATASET_BASE_SIZE and
SCRATCHPAD_L3 are part of the hash function, so a knob for "use
more RAM" would either do nothing or fork the chain. Threads are
the only real dial.

1 files changed, 2 insertions, 0 deletions

diff --git a/src/net.h b/src/net.h
index 4379d04..11c023e 100644
--- a/src/net.h
+++ b/src/net.h
@@ -58,6 +58,8 @@ int  BtfPexAccept(const std::vector<std::string>& vDesc);
 void AbandonRequests(void (*fn)(void*, CDataStream&), void* param1);
 bool AnySubscribed(unsigned int nChannel);
 void ThreadBitcoinMiner(void* parg);
+// Starts MinerThreadCount() miners; returns how many came up.
+int  StartMinerThreads();
 bool StartNode(string& strError=REF(string()));
 bool StopNode();
 void CheckForShutdown(int n);