Yup, I'm noticing that (I have a cheapo Azure VM doing ~8k/s,) but the 7302 has a pretty low clock (2.5GHz,) all things considered - I'm more surprised by how poorly the threads scale when they're on a single VM vs. multiples running on the same host. I get the feeling I have some tweaking to do...Dylan Chen wrote: ↑May 9th, 2021, 8:09 pmfor your reference, the apgsearch running on my WSL / 4600H (6c12t) could reach 8k in single thread, and the multi-thread could reach 60k in total.etmoonshade wrote: ↑May 9th, 2021, 12:42 pm62 cores * 1 virtual machine, 62 cores total: ~40k soups/second (s/s)
15 * 4, 60c: ~55k s/s (I think - didn't keep this data specifically)
7 * 8, 56c: ~75k s/s
So with my specific setup (an Epyc 7302 server at 32c/64t, running Hyper-V)
some tiny 1c1G server I rent from cloud (with AVX-512) could reach 9k+. you can check https://catagolue.hatsya.com/haul/b3s23 ... oud_Debian
each different number suffix stands for a 1c1G cloud server.
the haul size wouldn't be problem, it is not linear growing with the soup number. And the stability of Catagolue is fairly sound, it withstand 70 tiny server 'attack' in the size of 0.11billion soups.(haul size 53kB)
the interval I set for C1 is usually 2h+, and G1 is 0.5h.
As for the haul counts, thanks for the info - sorry if I'm focusing on this too much, I've just read a lot about people breaking stuff and I'm not 100% sure on the unspoken rules for doing something with multiple machines submitting hauls/etc.
Also, that haul suffix idea is clever, and I am totally stealing it. Eventually, next time I stop and rebuild everything.
Edit: I have powershell scripts now that do most of the build and setup for me on a VM server - would there be an appropriate place to release/post them (and presumably a second build script for a cloud server?) Would that even be useful for anyone?