Categories
- 17.3K All Categories
- 9.5K Mining
- 574 Pool Discussion
- 378 Promotional
- 1.4K General Project Discussion (non-technical)
- 485 Education
- 811 Protocol and Client discussion
- 170 web3-js
- 29 Whisper
- 16 Swarm
- 3 RLP
- 303 IoT & Hardware
- 1.2K Smart Contracts and Dapps
- 28 Serpent
- 359 Solidity
- 664 Projects
- 1.2K Reference clients code and builds
- 249 Eth & AlethZero- Cpp Implementation
- 471 Geth - Go Implementation
- 242 Mist
- 15 Node.js Implementation
- 36 Python Implementation
- 49 Mix
- 36 Other Implementations
- 170 Meetups
- 40 Other Events
- 226 Jobs & Skills
- 281 Press and Articles
- 75 Audio/Video
- 296 Ether Sale
- 1.2K Other Languages
- 96 Chinese
- 255 German
- 33 Italian
- 111 French
- 3 Hebrew
- 42 Japanese
- 75 Portugese
- 46 Romanian
- 185 Russian
- 231 Spanish
- 47 Turkish
- 125 Watercooler
Diminishing Returns on Getting Back to Sync?
JenBen
Member Posts: 2 ✭
Hi, sorry I know just a little more about Ethereum than I need to in order to get it running.
I am running Mist 1.7.2.
I let myself de-sync for a week and upon running the mist client / geth again, I've been going for 40 hours with 4 gb of ram usage with no end in sight.
My understanding is that starting a fresh install in --fast (also --light?) mode yields large time savings, but after that you are running as if you were a full node, which is sustainable as long as you don't fall behind (if you call 70 GB+ on an SSD sustainable).
It seems to me that for a hobby grade miner, there is a breakpoint where it would be faster to just delete your chaindata than it would be to try to sync after a lapse.
Am I accurate in this? Is there anything coming down the pike in ethereum development that will change this situation?
Thank you.
I am running Mist 1.7.2.
I let myself de-sync for a week and upon running the mist client / geth again, I've been going for 40 hours with 4 gb of ram usage with no end in sight.
My understanding is that starting a fresh install in --fast (also --light?) mode yields large time savings, but after that you are running as if you were a full node, which is sustainable as long as you don't fall behind (if you call 70 GB+ on an SSD sustainable).
It seems to me that for a hobby grade miner, there is a breakpoint where it would be faster to just delete your chaindata than it would be to try to sync after a lapse.
Am I accurate in this? Is there anything coming down the pike in ethereum development that will change this situation?
Thank you.