When you activate SBDF caching, it has a "cost" similar to scheduling Analysis.
You can check the Web Player caching settings and based on the filters you can find out how many of all your SBDF files are cached, if you know where they are, in the Library or on a file system... that is far from being intuitive.
In order to optimize the Web Player, we need to know how many schedules there are, but also how many SBDF files are cached. Otherwise we have to wait for the server to be strained to start thinking there might be too many SBDF files cached from library or from files.
Ideally, that information would be readily available in Monitoring & Diagnostics, or even (also?) under the Scheduling and Routing view, where an end-user would expect to find it.
It would be a great way to help optimize Web Players.