Version: `0.8.10`
OS & Version: macOS 10.12.4 (Sierra) 2,6 Ghz Quadcore I7, 16GB DDR3
Node type: `eth/geth 1.6.1`
After I installed Mist, the Node sync job started. At first it the process went very fast, but every hour the blocks per second drops. Currently is about ~1 block per second. Considering I need to sync 1M more blocks, it will take forever to sync it. What's causing this?

Beside that I'm seeing that my Chaindata folder keeps extending. Currently it's 92GB, but I'm only at 70% of the sync process. Is there something wrong? Or is it normal to have a wallet which is ~100GB?

Yea, I already posted this issue....
This BC is a COMPLETE POS!!! The wallet is even worse. It doesn't work with GETH nor does it work with Parity. WHAT THE FUCK IS GOING ON????? OVER A FUCKING WEEK INTO THIS POS!!!
Hello. i don't know what POS is, but this amount of data implies that you
are syncing on the full mode.
Please delete your ~Library/Ethereum/geth/chaindata and start geth like
this:
geth --fast --cache=1024
you can download geth on http://geth.ethereum.org. Then you can start Mist.
It should take on average 2h, maximum 4h.
On Fri, 26 May 2017 at 00:50 ejccna72 notifications@github.com wrote:
This BC is a COMPLETE POS!!! The wallet is even worse. It doesn't work
with GETH nor does it work with Parity. WHAT THE FUCK IS GOING ON????? OVER
A FUCKING WEEK INTO THIS POS!!!—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/mist/issues/2350#issuecomment-304184053, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAC4BJ179Z5Rmq6ENEZbWMiN2kqlzi3kks5r9kv7gaJpZM4Nm4da
.
I'm guessing POS is (Peice of Shit), Not a way to get issues resolved :(
@evertonfraga that worked perfectly. Thanks you so much. I know finally see my Eth in my wallet.
PS. For the people with similar issues: This youtube movie helped me to start geth in fast mode.
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.