Quote from: theduuude on September 26, 2016, 04:42:50 AM

Quote from: IncludeBeer on September 25, 2016, 08:47:46 PM

Quote from: Cobra98 on September 25, 2016, 06:53:05 PM

Ahhh just thought it was something different with command line. I've only got an I5 2500k and see a max of 6000 nonces/min with 4 threads but have never used the async option.

Quote from: IncludeBeer on September 25, 2016, 06:25:10 PM

Nothing tricky in my .bat:

Code:

wplotgenerator 4163282010088137402 76054000 7625000 25000 10 /async
PAUSE

I think it's more just high-end (and well overclocked) cpu. Also, put in async mode, so plots are still being constantly generated, even when they're also being written to disk. With gpu plotter, there's a lot of down time on the gpu because no plots are created while they're written to disk. So ya, faster (and I imagine cheaper) plotting with cpu plotter.

Of course, the gpu plotter has capabilities to use lots of gpus and to write lots of plot files to different directories at the same time...

Ya, I'd imagine the only differences are in the cpu's. And to be fair, once the plotter was done with the plot i posted, it ended up being 30k nonces/min.

...and amount of ram, if you run out nonces/min will suffer. i've had best plot speed with stagger = ram/2

Makes sense....As I always run the optimizer on my plots, I'm not so concerned with stagger size though. When plotting, I just just pick a sufficiently large stagger that will divide into my plot size evenly (typically 10k-25k).