I was looking at Dusk’s prover requirements like I was shopping for a gaming PC.
16 cores?
I thought that meant a proof could throw all 16 at the problem.
Then I found the awkward part.
Proof generation is single-threaded.
So a 16-core machine doesn't make one proof a 16-core job.
Then I noticed the other part of Dusk's requirements: prover performance is tied to how many workers the server can run simultaneously, with one CPU core specified per worker. That made the 16-core number feel very different.
The cores aren't simply making one proof faster. They're giving the prover more room to handle multiple proving jobs at the same time.
And suddenly I realized I'd been reading the hardware requirement as one number:
How fast is this prover?
But there are two very different questions hiding underneath it.
How quickly can one proof get through its work? And: How much proving work can the machine handle concurrently?
I thought 16 cores answered the first question. It doesn't, at least not by itself.
@Dusk_Foundation
$DUSK #dusk
16 cores?
I thought that meant a proof could throw all 16 at the problem.
Then I found the awkward part.
Proof generation is single-threaded.
So a 16-core machine doesn't make one proof a 16-core job.
Then I noticed the other part of Dusk's requirements: prover performance is tied to how many workers the server can run simultaneously, with one CPU core specified per worker. That made the 16-core number feel very different.
The cores aren't simply making one proof faster. They're giving the prover more room to handle multiple proving jobs at the same time.
And suddenly I realized I'd been reading the hardware requirement as one number:
How fast is this prover?
But there are two very different questions hiding underneath it.
How quickly can one proof get through its work? And: How much proving work can the machine handle concurrently?
I thought 16 cores answered the first question. It doesn't, at least not by itself.
@Dusk_Foundation
$DUSK #dusk