Running HF20 on my witness

in witness-category •  6 years ago 

There is little time for the upcoming HF20 activation date. After the fix for the recent blockchain halt, I have switched my witness node from 0.19.12 to 0.20.1 and produced a block already.

$ steemd -v
steem_blockchain_version: 0.20.1
steem_git_revision:       de88134b69e50d5d4cd56484a56f00fa16faef78
fc_git_revision:          de88134b69e50d5d4cd56484a56f00fa16faef78

------------------------------------------------------

            STARTING STEEM NETWORK

------------------------------------------------------
initminer public key: STM8GC13uCZbP44HzMLV6zPZGwVQ8Nt4Kji8PapsPiNq1BK153XTX
chain id: 0000000000000000000000000000000000000000000000000000000000000000
blockchain version: 0.20.1
------------------------------------------------------

I do manual builds and compiling, so fetching the v0.20.1 tag, and compiling it is enough. Migrating from 0.19.12 to HF20 requires a blockchain replay.

I see some other witnesses complaining about the long replay times, so dropping here my stats for the reference:

My server's CPU: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz and it took 3 hours, 40 minutes to catch up with the block production.

Vote for me as a witness


I have been losing my pace on witness rankings, lately.

I do my best to support the blockchain with my skills. If you want to support me for my witness run, consider casting a vote on either via Steemconnect, or steemit.com. The world will be a better place after that.

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Good evening sir, I was wondering if the http://monsters.steeminator.com/ website is down due to something with the latest Steemit downtime issue or because of the Alpha to Beta of Steem Monsters or is it gone now? Thanks!

He cryplectibles, It's gone. I have lost my interest on Steemmonsters lately so and keeping up with the changes were requiring development time. Sorry about that.

:(
Another 36 hours for my node to lose
:(

Get an i7 :P

Earliest next year February, when the old contract is running out

36 hours?

Sadly yes.
1 CPU core 100% busy.
No waiting time for IO. Disk is not that busy, when in replay.
At least that what nmon shows and I trust nmon.
The only slow factor seems the CPU.
( I have SSDs in my node)

model : 79 model name : Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz stepping : 1 microcode : 0x1 cpu MHz : 2199.998 cache size : 16384 KB

The replay is mostly single threaded, so cores won't make a big difference but the speed of the core is critical.

How much ram?

@emrebeyler hocam size özelden nasıl ulaşabilirim.

Posted using Partiko Android

Got my vote still @emrebeyler Keep up the community support :)

I know mate, thanks!

I received your message! I appreciate your effort. How is your server set up? or servers? Just curiosity
Not much but i will give you my vote, hope you can get some impulse, good luck

Thanks! Every bit helps. :)

Regarding server specs:

RAM:    64 GB DDR4
Hard Drive: 2 x 2 TB SATA 6 Gb/s 7200 rpm HDD Class Enterprise 
(Software RAID 1)
Connection: 1 GBit/s-Port
Guaranteed bandwidth:   1 GBit/s
Backup space:   100 GB
Traffic:    30 TB *