5

Last night, I updated to a much newer version of the Mist Ethereum wallet than when I last used it (0.2.6 to 0.8.9) about 1 year ago, and from everything I've read on DAG size, it's using far more space than it should be (which is why I was never able to run it off my SSD previously - it would eat 10+ GB and get too close to the 90% mark of my puny 128GB boot drive, and I'd have to cancel it).
Last night, I finally figured out 'mklink', and the DAG is happily syncing away, thinking it's in %appdata% when it's actually being pointed to a spot on my spinning disk drive.

The wallet app seems fine with this. It recognized right where I was as far as the last time I synced the DAG, and proceeded from there (I had just under 1M blocks to go, as of 4 hours ago). I made a note of how much free space I had when I began the sync process, so I'd know how much it was taking up.

Fast forward to now: When I wrote it down, I had 360GB free on the HDD I'm using. As of now (75.7% sync), I'm down to 337GB free, or around 23GB of DAG. Accordingly, the 'chaindata' folder it is syncing to is exactly 30GB at time of writing (7GB having been downloaded 1 year or more ago).

This is the same behavior I was seeing before relocating the DAG using mklink, so I don't believe that has a anything to do with it - in fact, I haven't ever had a fully synced DAG on my PC (only my mining rig, over a year ago when it was much smaller), because it would never fit on my paltry remaining SSD space.

If it helps diagnostically, the 'chaindata' dir contains 16,060 items (and counting), each approx. 2MB, and starting chronologically with 047061.LDB (in 2016), up to the present 191120.LDB (quickly being usurped by newer files).

Any ideas?

Thanks very much,

-Aaron

Edit: Sync now 86% complete, /chaindata up to 36GB

Edit2: Sync now 98% complete, /chaindata up to 43GB

4

I think you may be confusing the DAG with the other chain data. The DAG is only used for mining and will only take up about 2GB. What is taking up the space is the whole blockchain, which you are currently downloading (that's what "syncing" is. 40 GB is about right, and until light clients become available, that's just something you'll have to deal with. The chaindata folder will continue to grow, at a slower rate, even when you are done syncing.

  • Yes, I was indeed confusing the two - mainly because when I used the command line: geth.exe --datadir [desired location], the initializing text for geth read "Data Location: [new desired location]. DAG location: [old %appdata% location], and the c:\ drive continued to grow at the same rate (which would've filled it long before the chain finished syncing). Now that I figured out how to "fool" the wallet using mklink, I can keep the /chaindata/ on a drive with plenty of space, but I was still mistakenly under the impression that DAG was synonymous with the chaindata. Thanks! – Aaron May 4 '17 at 23:15
-1

I'm actually new here and had a few questions. A 100GB seems to not be enough to do this kind of operation. Is there a way to slim and optimize this process?

I'd rather only use 2-5GB and still be able to mine.

  • 1
    Please search the site and if you don't find what you're looking for, ask a new question. – Daniel Jun 2 '17 at 4:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.