View in context in the libbitcoin Slack #general mirror.
secp batching in concurrency window default (50k blocks), on maxi. Concurrency model seems to be working nicely, mostly 100% CPU since startup. Averaging right around 317,000 signatures per second in each block. The maxi has 64 x 2.1 GHz threads, and note that we are not pausing other operations during batch processing, the node continues to download and confirm - only validation is suspended during the periods of batch processing.
I expect and it appears that this baseline will be slower than our traditional runs. The batching incurs overhead in buffering the signatures to mmap and in post-processing the results, in CPU, RAM and I/O. However GPU processing this same work will free most of its CPU cost and complete in fraction of the time. At block 450k the signature verification cost is about 8 minutes. That should come down to 30 secs on a typical modern GPU (not maxi), and just a few seconds on a high end GPU system.