12-15-2021 12:18 PM - last edited on 02-10-2022 10:20 AM by OSAdmin
We are looking at the performance of several huge base data imports. What are the best practices for setting cache page size and cache pages-in-memory limits for the best possible import performance? We have broken the data load up into >40 separate imports but we still have some imports taking over 40 minutes. I am hoping there might be other ways to improve the import time without having to break the data imports up further.
Solved! Go to Solution.
12-15-2021 08:08 PM - edited 12-15-2021 08:09 PM
Hi,
As Jon mentioned, trial and error is almost always necessary. That being said, here are some general guidelines that are documented in the OneStream Foundation Handbook on pages 379-380.
Cache page size and cache pages in memory guidance:
Nick Kroppe
OneStream Software
12-15-2021 01:11 PM
Perhaps someone else can provide a better method, but I have always used good ole trial and error to find the optimal settings. Keep adjusting until you find the sweet spot. I know this can be cumbersome on a 40 minute data load as you have to wait for it to finish each time but that's the only way I know.
12-15-2021 08:08 PM - edited 12-15-2021 08:09 PM
Hi,
As Jon mentioned, trial and error is almost always necessary. That being said, here are some general guidelines that are documented in the OneStream Foundation Handbook on pages 379-380.
Cache page size and cache pages in memory guidance:
Nick Kroppe
OneStream Software