Careful when upgrading delegate to 0.4.25

[vikram]

[URGENT] Delegates Please Revert Upgrade!

https://bitsharestalk.org/index.php?topic=7067.msg161312#msg161312

https://bitsharestalk.org/index.php?topic=7067.msg161432#msg161432

All community members please help spread the word.

[abit]

It seems that a fork occurred before expected (<1249400).
All delegates should upgrade. Other users should upgrade as well. Wish the binary releases asap.
@vikram.

[svk]

I've updated the release notes to include a note about the memory requirement: https://github.com/BitShares/bitshares/releases/tag/v0.4.25

This doesn't appear to be true for reindexing and syncing, I've successfully reindexed and sync my seednode which has 512mb RAM and 4gb swap.

I compiled it on my personal computer which has 8gb of RAM so no issues there.

[ripplexiaoshan]

I am using 2GB VPS, and it seems fine for both compiling and running, but my delegate keeps missing blocks while the wallet is up，according to bitsharesblocks.com.

[emski]

0.4.24 instances report a lot of duplicate transactions when blockchain_use_forks is used. Is it the same with you ?

[svk]

Our delegate is running fine, but it is consuming a lot of virtual memory (2.3GB, but doesn't seem to be increasing) during initial sync. My best guess is that the people with problems are swapping due to insufficient memory. We already suspected a leak in the previous client during syncing (last client required 1.6GB on windows for initial sync).

Are the forking issues related to the new fork resolution code? Maybe the fact that the old and the new are live at the same time?

[abit]

EDIT.
Compiling.

[btswildpig]

I've updated the release notes to include a note about the memory requirement: https://github.com/BitShares/bitshares/releases/tag/v0.4.25

will delete the blockchain before upgrade helps ?

[vikram]

I've updated the release notes to include a note about the memory requirement: https://github.com/BitShares/bitshares/releases/tag/v0.4.25

[Riverhead]

yep, I think 3 to 4GB is a good minimum requirement for now for delegates, until we can isolate the cause of the heavier memory requirements.

Agreed. Going to upgrade.

[dannotestein]

yep, I think 3 to 4GB is a good minimum requirement for now for delegates, until we can isolate the cause of the heavier memory requirements.

[Xeldal]

My 1GB instance is continually crashing while syncing, Initially this crashed and (appeared to be) locked up.  I had to restart

My 4GB instance hasn't crashed at all.

[Riverhead]

It's possible the box may have come back. The delegate I had running on that box started missing blocks because nothing else could be processed.

I have it syncing on another box now and once it's all up to date I'll turn that on as the block signer and update my version number.

[dannotestein]

Our delegate is running fine, but it is consuming a lot of virtual memory (2.3GB, but doesn't seem to be increasing) during initial sync. My best guess is that the people with problems are swapping due to insufficient memory. We already suspected a leak in the previous client during syncing (last client required 1.6GB on windows for initial sync).

[Riverhead]

PM me your skype id?