# Archival Node Sync Time

**URL:** https://forum.algorand.co/t/archival-node-sync-time/3059
**Category:** General
**Created:** [April 20, 2021, 2:58pm UTC](https://forum.algorand.co/t/archival-node-sync-time/3059 "2021-04-20T14:58:20Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![tsachi](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/tsachi/32/29_2.png) [@tsachi](https://forum.algorand.co/u/tsachi)
#### Post date: [April 20, 2021, 3:45pm UTC](https://forum.algorand.co/t/archival-node-sync-time/3059/6 "2021-04-20T15:45:11Z")

</div>

The documentation sometimes get lagged behind the code. You can look [go-algorand/config.go at master · algorand/go-algorand · GitHub](https://github.com/algorand/go-algorand/blob/master/config/config.go) for the parameter description.

Please let me know if you have any other questions. ( I think that the in-code documentation would answer your question from above )

As a one-liner : setting CatchpointTracking to -1 would prevent archival nodes from tracking the catchpoint label for the node. Depending on your usage, you might want to restore this up once catchup is complete. Disabling this feature reduces the amount of disk i/o being performed. If the botteneck on the catchup on your machine happen to be the disk ( which I believe is the case ), then setting this to -1 would improve your node’s catchup performance.

---

_[View the full topic](https://forum.algorand.co/t/archival-node-sync-time/3059)._