I have this issue. After Effects CS6 doesn’t clean his cache/temp files when you close the application. I get gigabytes of leftover files on disk each day. Anyone knows something about this?
edit:
for some reason the disk cache was on. turned off, problem solved. Also there is a button to clean the cache files manually, but who knows why they didn’t add automatic clean up on application exit.
doru saidbut who knows why they didn’t add automatic clean up on application exit.
it would make the disk cache feature useless.
Well,it’s useless the most of the time anyway 'cause it doesn’t work the way it should.
Maybe the next update will fix these issues.
doru saidI have this issue. After Effects CS6 doesn’t clean his cache/temp files when you close the application. I get gigabytes of leftover files on disk each day. Anyone knows something about this?
edit:
for some reason the disk cache was on. turned off, problem solved. Also there is a button to clean the cache files manually, but who knows why they didn’t add automatic clean up on application exit.
Doru if i understood the question right the answer is located in the first minute of this video
I hope this helps, cheers 
Maybe it has something to do with the global cache performance? It keeps previously rendered key frames even after closing the application. By cleaning the disk cache on exit you delete all the data that was saved by After Effects. That’s what the cache is there for - to speed up your workflow by not rendering already processed frames. It’s like a the most valuable feature CS6 has to offer… I would not turn it off if I were you.
I love disk cache… I don’t know why would you turn it off. Just clean it when you are done working on a project.
InlifeThrill saidIt’s like a the most valuable feature CS6 has to offer… I would not turn it off if I were you.
+1
now I see why they didn’t delete the cache on exit, that video explained all, this restore between sessions is useful after all.
doru saidThat's the whole point (and brilliantness) of CS6 persistent disk cache.now I see why they didn’t delete the cache on exit, that video explained all, this restore between sessions is useful after all.
If you really want to take advantage of it, install a modest SSD drive in your computer as a dedicated disk cache drive. It feels a bit like having 256GB of RAM.
I’ve been having hard time with CS6 lately. Had to switch to 5.5 a few times. Even the global cache is acting weird now and then. Not to mention the ever popular slow ram-preview thing. The most annoying of them all should be the freezing ram preview at 1-2 rendered frames only. You clean the disc cache manually, purge and then try again. At the end your restart the app. These have not been addressed in the latest update even though the forums are full of people complaining. Oh well…
InlifeThrill saidthat's what i meant in the 1st post.I’ve been having hard time with CS6 lately. Had to switch to 5.5 a few times. Even the global cache is acting weird now and then. Not to mention the ever popular slow ram-preview thing. The most annoying of them all should be the freezing ram preview at 1-2 rendered frames only. You clean the disc cache manually, purge and then try again. At the end your restart the app. These have not been addressed in the latest update even though the forums are full of people complaining. Oh well…
felt_tips saidThat’s the whole point (and brilliantness) of CS6 persistent disk cache.
it’s hundred of miles away from being brilliant mate.
In what specific ways is the global performance cache not working for you?
If you’re encountering problems, be sure to submit bug reports here:
http://www.adobe.com/go/wish
Make sure that you’ve installed the latest updates ( http://adobe.ly/lsrkmJ ). They fix a lot of problems.
I am up to date Todd. I am pretty sure the issues we are speaking of are well known. I described a few of them in the thread your previously started. Here it is again: http://videohive.net/forums/thread/ssd-experience/65285?page=7#645685
Another thing - it often happens that the global cache simply switches off for an image sequence after I used “reload footage” on it. I can ram preview it, but the green/blue bars disappear as soon as I’m done playing it, it just does not keep it. I’ve got plenty of disc space. Nothing helps until I restart. Then it’s fine… but that’s beyond what’s practical here and it sure is enough to drive me away from CS6. I user should not be going through that much trouble to get his work done.
@Inlife,
Sometimes, global performance cache decides that it’s quicker to read footage directly from disk than to cache it to the cache disk. If that’s the case, you will see a green line in RAM, but not a blue line. Global performance cache tries to reserve the disk cache space for the more processor intensive operations.
Maybe it’s a real bug (in which case get a reproducible case and report it), but check you’re not worrying about a non-existent problem. In my experience, there were a few bugs in the caching (for some specific third party plug-ins and some specific expression situations), but I think they’re mainly (or all) fixed in the latest update.
@didgi
Be specific, otherwise you’re wasting your time.
Hey,
well it happened with a project that uses no external footage whatsoever… As said earlier, I could live with slower ram previews… the global cache compensates for that more or less. The problem comes when the cache itself stops caching. Then I lose the point of it all and switch back to 5.5. No global cache there, fine. It works as expected. I do my best to understand the software beyond the buttons in the interface but when it comes to some random interpretations of issues and me trying to fix it on my own (because there is no clear answer to what cause it, I checked), I’d rather just stop. It should not be that had. I’m a little irritated, I admit.
InlifeThrill saidHey,
well it happened with a project that uses no external footage whatsoever… As said earlier, I could live with slower ram previews… the global cache compensates for that more or less. The problem comes when the cache itself stops caching. Then I lose the point of it all and switch back to 5.5. No global cache there, fine. It works as expected. I do my best to understand the software beyond the buttons in the interface but when it comes to some random interpretations of issues and me trying to fix it on my own (because there is no clear answer to what cause it, I checked), I’d rather just stop. It should not be that had. I’m a little irritated, I admit.
Sounds a bit like a bug. But it might also be that the compositing of the layers is such a “cheap” processor operation that it’s being done live, while the layers themselves are being cached. It maybe that this is quicker than reading uncompressed cached frames from disk. What kind of disk is your cache disk? SSD?
When it fails to cache, are you then finding that a subsequent RAM preview is taking lots of time to recalculate the frames… or are they there just about immediately? In other words, is it about the indicators or about the performance mainly? I’m still wondering if the issue with it not working like you expect is to do with a problem or with your expectation. Are you expecting to always see a blue line?
I’m not saying that it’s not a bug or that Ae is perfect, but I know when I started using CS6, I had lots of similar issues with global performance cache, and how it was visualised that turned out not to be issues. At fault was my expectation of how it should be visualised.
Seriously though, if you think it’s a bug, file the bug with Adobe and it will be looked at.
I see. Well I use the OCZ REVODRIVE 3 PCI-EXPRESS SSD with 30GB set for AE.
I’ll give it more time. It just acts erratic. Most of the things seem unprovoked. Cached frames disappearing for no reason, ram preview not starting at all… That’s what bugs me so much, I guess. Anyhow, thanks a lot for the time. This was not supposed to be big of a deal. Should be fine.
I’ve noticed today that AE doesn’t use all the power the computer have. The CPUs are around 30% where C4D keeps them at 97% 100%
Is this normal? Why it doesn’t use the rest of 70% and finish that render faster?
Why it doesn’t use the rest of 70% and finish that render faster?
The CPU isn’t the only possible bottleneck. The bottleneck could be at any point in the data flow: slow disk, slow disk bus, insufficient RAM, slow RAM bus, slow GPU, slow VRAM bus…
See this about performance bottlenecks:
http://www.video2brain.com/en/lessons/overview-of-data-flow-and-common-bottlenecks
That video is in a 1.5-hour series about performance in After Effects. I recommend watching the whole thing. (It was for CS5.5, so it doesn’t have global performance cache or ray-traced 3D renderer information in it, but nearly all of the principles are still relevant.)
Actually, this is a better place to start for performance information, since it links to the above video series and to some more recent materials about CS6:
http://blogs.adobe.com/aftereffects/2011/02/optimizing-for-performance-adobe-premiere-pro-and-after-effects.html