for some reason, if old dag files exist when i start ethash, it has 0H/s and tends to hang/crash the moment it gets new work from the pool
is there a reason for this? i considered adding a rule to the batchfile to delete all pre-existing DAGs at launch
is there a reason for this? i considered adding a rule to the batchfile to delete all pre-existing DAGs at launch
The generation of the DAG file is a very slow process if you use a slow CPU. So it is better not to delete the DAG.
takes <5 minutes per dag - not that bad assuming you plan to be mining for hours or days on end
For the Intel G1620, it take about 30 mins to generate one DAG. So it is better not to delete the right one.
