For testing, I'm running a private chain on my laptop. I've loaded a contract and I'm simulating a heavy load on my geth instance by submitting 500 transactions. All the transactions are submitted over ~15 mins or so but while the transactions are coming in mining grinds to a halt and no new blocks are created. It doesn't seem to matter if I'm using
ethminer -C -t 1 to start ethminer in a different process.
All the transactions are happening under the same address so it's not like the miner has a hard decision when it comes to picking what transactions go in the next block. It just has to handle the nonces in order. Eventually mining picks back up again but that can take 20 mins before it happens.
If it matters, I start geth v1.7.1 with the following flags:
geth --networkid 3141 --rpc --rpcapi "db,eth,net,web3,miner" --rpcport "8545" --rpccorsdomain "*" --datadir "~/eth/data" --port "30303" --nat "any" --identity "MyNode-1" --rpcaddr "0.0.0.0" --gasprice 0
geth doesn't print out any errors. Why does mining stop while a large number of transactions are being received?