Generating DAGs in epochs 472 and 473

[konstiantyn]

I'm not sure what is problem. I really don't know if the pool works correctly or not. Pool hashrate dropped from 40GH/s to 0.

[konstiantyn]

Again generating the DAG in epoch 472.

[MiningCryptoLive]

I am going to test this tonight but thought I would throw this out there.

According the Geth command line options the node when synced keeps 2 dag's on disc. default location is ~/.ethash
you also have the option to add dag's in mem using --ethash.dagsinmem (value) default is 1.

So we should be able to set the config file dag directory to ~/.ethash and miningcore should pick up the dag from the nodes dag directory instead of generating it. Correct me if I am wrong but I think this should work.

[oliverw]

That won't work currently but its an interesting idea to implement.

[MiningCryptoLive]

It would definitely help. Right now when a new dag comes we have to stop mining on the pool until the new dag generates. Which is sometimes close to an hour.

[oliverw]

Could you check if the latest dev branch improves dag generation times?

[MiningCryptoLive]

DAG Generation is still as slow on dev-branch as it is on the release branch.