Page 1 of 1

Performance breakdown when cache is full

PostPosted: Tue Jan 12, 2016 2:25 pm
by Stephan Haitz
Hello,

I got following problem: I have a flow with a resolution of 780 x 284, nothing special but 7500 Frames. When I start to render, Fusion renders quite fast until the memory occupancy reaches a certain amount. And then it´s rendering like snail. A slow snail. When I stop the rendering it takes quite a while to stop and it takes quite a while to purge the cache. When I start rendering again at the point it starts rendering fast until cache reaches this special limit. (Machine: i7 3930, 12 Cores, 32GB RAM).
I tried to get some different results with the memory settings, but didn´t help to much: As soon as Memory allocation reaches the percentage of the Cache Memory Limit there is the Break-In.

What can I do to avoid this performance break-in?

Many thanks

Stephan

Re: Performance breakdown when cache is full

PostPosted: Tue Jan 12, 2016 2:42 pm
by Stefan Kirste
got the same problem, but not at all, only by some scripts...
but i didnt solve the problem by myselfe, yet :/

Re: Performance breakdown when cache is full

PostPosted: Tue Jan 12, 2016 8:32 pm
by michael vorberg
you could try to add this expression into the "frame saved script" of the loader

Code: Select all
fusion = eyeon.scriptapp("Fusion", "localhost")
fusion.CacheManager:Purge()


this will purge the cache after each saved frame

Re: Performance breakdown when cache is full

PostPosted: Wed Jan 13, 2016 10:27 am
by Stephan Haitz
This should be the same as limiting the cache to 0% of physical RAM, right?

I also have the feeling, when I use a real small cache (~5% of physical RAM) stuff works a little bit better.

But in my Case the Cache is also quite usefull until it is full...

So we have to live with it?

Many thx and best regards

Stephan

Re: Performance breakdown when cache is full

PostPosted: Wed Jan 13, 2016 2:43 pm
by Stefan Kirste
cache to 0% or purgecache is a workaround, but not the best solution, because u can loose performance of cached branches that didnt need a update for some frames.
I hope, that is a kind of bug, and maybe its gone in Fu8 ?