Quote:
Originally Posted by jackoneill
How many frames did you filter? The cache reevaluates its behaviour every few hundred frames, so the speed/memory consumption may improve (or degrade) over time.
|
I noticed that, the other day. The other day I set
core.max_cache_size = 4096
(Using TempLinearApproximateMC), just to see what would happen. Python started off at ca 6G (as expected for the job), but slowly tapered off to almost not using the cache at all. Seems Python is clever enough to realize what it actually needs, over time. I like that.
(And kinda logical too: it is, after all,
max_cache_size, not just cache_size).