GitKraken commit history page size across local and remote branches

The goal is to confirm whether GitKraken's configured commits-per-page limit applies consistently across local commits and remote-tracking branches in the commit graph view.

The pagination control appears as numbered buttons, with an optional infinite-scroll or Load-more alternative. Documentation indicates the setting may not apply uniformly across repository types or branch states, but it does not specify whether switching from a local branch to a remote-tracking branch resets or preserves the page size and current offset. This should be confirmed against the installed client because the documentation does not state whether the limit is branch-scoped.

This matters for large repositories where rapid page loading can affect responsiveness. The question assumes the standard GitKraken desktop commit graph and does not cover submodules or custom merge views.

Does the commits-per-page preference remain active when moving between local and remote branches? Is the page offset retained across branch switches? Should teams disable infinite scroll for very large histories to avoid repeated full-history loads?