I have thousands of people using Valentina as the database engine, and as you can imagine their needs vary enormously. I set a default database cache size on startup, but in my app's preferences offer the ability of the user to increase it if the database grows too large. This is pretty clunky, because (1) you have to guess what the optimal size is, and (2) my users are often not comfortable with computers and don't even know this is an option (or want to play with it). When they do, they have to set it, relaunch, play with the app bit, try a new setting, relaunch, etc., until they iteratively figure out the best cache size.
My request (which I've made in the past), is that Valentina automatically configure the cache size based upon the needs of the database. That is, once loaded, resize whatever the default is to accommodate the extra data, if needed. I suspect there is no straightforward way to do this, but it should be possible for Valentina to make a educated guess about the suitability of the cache size. Even something simple, like assuming that a 10 MB cache is inadequate for a 200 MB database, would be step in the right direction.
Another option would be for Valentina to monitor memory use and send an alert to the app that increasing the cache would speed things up. Then the app could increase the cache size on the next launch, alert the user, or whatever the developer thought was best.
What do you think?