Understanding Memory Thrashing

Thanks GilbertQ...

My average memory usage, for the whole capacity, is 6 GB. Looking at the line chart, generally it hovers between 5 to 7 GB.

The two large datasets are refreshed every 2 hours, around the clock. At periods during which one of the large datasets is being refreshed, memory usage for the capacity typically goes up to around 7 GB. Occasionally the dataset refreshes take longer than usual, and the refreshes of the two datasets overlap; even when both datasets are being refreshed simultaneously, memory usage for the capacity typically does not exceed 10 GB.

Looking again at the memory usage data export...which shows memory usage for each three-minute period during the last week...there were only 16 "three-minute periods" (out of 3,360 periods) where memory usage exceeded 10 GB. Maybe those were periods of high report consumption, and/or data refreshes -- I'm not sure.

All of that is just to say that it seems like my datasets are never "sitting at above 12.5 GB" -- right? So again, I can't figure out why there would ever be dataset eviction/thrashing.