Based on the link you have, I think you already have tried Prefetch config, but just in case, I will include it.
Prefetch cache is the amount of data that Sitecore will load before anybody makes any data requests. The more you prefetch, the slower your startup will be but the less likely that a page request will need to load data. Also, the more you prefetch, the more system memory you use and the more data requests ping the data layer at startup. In general, you need to tweak this to a level that gives you an acceptable start up time, and doesn't consume all your system memory or pin your database. Or you may need to add more memory if you need more cache for some reason. Other items are loaded into cache after startup as needed.
You alter the amount of prefetch by using a config patch to change the value of the prefetch cache size. Here is a version of the example from the docs:
<database id="web" role:require="ContentDelivery or Standalone">
Reference the prefetch configuration docs here: https://doc.sitecore.com/xp/en/developers/102/platform-administration-and-architecture/configure-prefetch-cache-values.html
You can also look to optimize what gets prefetched by configuring specific templates and item paths to load. This way you can prefetch only the pages you know are visited most often. You can see docs about this here: https://doc.sitecore.com/xp/en/developers/102/platform-administration-and-architecture/optimize-or-disable-the-prefetch-caches.html