Okay, this is reassuring to hear it is expected behavior. Will be interesting to see how this evolves over time as archival nodes become prohibitively large for individuals to run, and even for enterprises to catchup with for archival purposes.
What does CatchpointTracking mean? When looking at node config documentation I cannot find this parameter. Furthermore, how does setting this parameter to -1 speed up catchup performance for an archival node?