snowmanam2

I did some testing on my FX-8350 (mostly "y" revision, but the "z" seems similar) and got the following timing results (with updated numbers from mine for comparison): N=12: 8s...

The default run mode is to total the polycubes in the "thread_pool_push_output" function. The worker threads call this after processing each polycube of size N-1. The generated cubes themselves are...

For the write performance, I think there might be a few different factors at play. I experimented by increasing the write buffers (WRITE_COUNT) in "thread_pool.c" and it seems to have...

The progress updates were there for normal "bottom-up" generation, but I disabled them for input cache files because I didn't know the input file length. I found ways around that...

For the data race / locking stuff, I actually tracked down the fairly cryptic ThreadSanitizer warnings I got to overflowing the input buffer in the new zlib input stream implementation....

Sorry to interject here, but I just want to confirm the correctness of NailLegProcessorDivide's result. I, too, got `3516009200564` for N=18, while simultaneously producing `457409613979` for N=17. Results for N=13...