Don't try to over-think this. Do you worry about managing what's loaded into RAM, or the caches of your CPU?
The SSD in a Fusion Drive is basically managed the same way as RAM. The SSD contains data blocks, not entire files or apps - just as RAM does - only those parts of a file that are actually
needed are pulled from the HDD. No need to load an entire app, which contains all sorts of stuff that you may never need, like localization (spoken languages) or features you never use. If a block has to be moved from HDD into RAM it is also moved into SSD, on the theory that, if the block is needed once, it will be needed again. As with RAM on a Mac, the block will stay on the SSD until something with a higher priority comes along - it's better to leave it in-place than to fetch it a second time from the slow HDD. The difference between RAM and SSD is that there is a lot more SSD than RAM, so the items that are moved to SSD will remain there far longer than they'd remain in RAM. So, if they're needed in RAM again, there's a good probability that they're coming from SSD rather than HDD.
About the only type of data that doesn't benefit from this is streaming audio/video. However, as soon as you hit pause or rewind, it will benefit from Fusion.
Let the computer manage this - there's no way anyone can possibly manage storage on the kind of micro level the computer can. The computer "knows" exactly what is needed, exactly what has been used. It's a mechanical, dispassionate, mathematical process that is not colored by our poor, human impressions of what, exactly, is happening inside our computers at any given microsecond.
Do not "break" a Fusion Drive. Like RAM, SSD is an expensive resource, and the end-user does not have the tools to manage that resource as efficiently as the OS can. Period. If you believe otherwise... try managing your CPU for a while.
[doublepost=1500108112][/doublepost]
How?
By the way, let's say you install Firefox, it means there's no possibility to download it on the HDD instead of SSD? I suppose it wouldn't make a difference if Firefox is often used and automatically goes on SSD.
What else goes on HDD if Fusion Drive automatically put stuff when something is often used? I suppose .JPEG pictures... but app "Photos" on SSD?
When you install
anything, it's going onto HDD. Only if it's needed in RAM will it make its way to the SSD.
Consider it to be an experiment - the first time the data/code is needed, it's moved to SSD on the speculation that it will be needed again. Since we don't know the future, we don't know if it'll be needed again. If it is needed again sometime soon, we're rewarded for having it in SSD, and it will renew its "lease" on SSD space. Meantime, if a new "tenant" comes along, whoever is farthest behind on the "rent" will be evicted first. If no new tenants show up, maybe the guy on the bottom of the list manages to come up with another rent payment in time to stave-off eviction. And if someone is evicted today and shows up with the rent again two hours later, they're let back in, without prejudice.
Fusion does not make its decisions based on "is this an app, or is this data?" Whether it's app or data, if it's needed by the CPU, it's loaded. If it's not needed, it stays where it is. You can safely assume that any part of an app or data set that is regularly needed will spend time in SSD. If it's seldom needed, the odds of being in SSD are lower, and if it's never used it
will be on HDD (like all the bad photos you can't bring yourself to delete, or the songs from an album that you never want to hear again).
This is a statistical process, based on the notion that whatever is used once will probably be used again. The more frequently that item is used, the higher the probability that it will forever remain in SSD. There will always be exceptions - but that's the nature of probability; nobody knows the future.