[CHORE] Imporve fast sync config params

Author: KonradStaniec

src/main/resources/application.conf

@@ -285,7 +285,7 @@ mantis {
 
     # Retry interval for resuming fast sync after all connections to peers were lost
     # Also retry interval in regular sync: for picking blocks batch and retrying requests
-    sync-retry-interval = 15.seconds
+    sync-retry-interval = 0.5 seconds
 
     # Response time-out from peer during sync. If a peer fails to respond within this limit, it will be blacklisted
     peer-response-timeout = 3.minutes
@@ -319,7 +319,7 @@ mantis {
 
     # During fast-sync when most up to date block is determined from peers, the actual target block number
     # will be decreased by this value
-    target-block-offset = 500
+    target-block-offset = 128
 
     # How often to query peers for new blocks after the top of the chain has been reached
     check-for-new-block-interval = 10.seconds
@@ -329,7 +329,7 @@ mantis {
     fastsync-block-chain-only-peers-pool = 100
 
     # time between 2 consecutive requests to peer when doing fast sync, this is to prevent flagging us as spammer
-    fastsync-throttle = 0.3 seconds
+    fastsync-throttle = 0.1 seconds
 
     # When we receive a branch that is not rooted in our chain (we don't have a parent for the first header), it means
     # we found a fork. To resolve it, we need to query the same peer for previous headers, to find a common ancestor.