Today, if we want to make sure a specific database is more in-memory than others, we can built is as a 16K or 32K block size (while all others are the default 8K block size) and then assign an amount of "cache buffers" to 16K block DBs.
I would like to see for ANY database, the ability to have a separate "cache buffers" allocation. This will allow having better control on data that is more frequently used without the need to change the block size (which is sometimes not sutiable for the data structures on that DB)
Thank you for submitting the idea. The status has been changed to "Needs review".
Stay tuned!
Timo,
>> "does not have suitable amount of memory available"
Having "enough" memory for cache buffers is not always possible (not applicable for very large-scale environments that has many databases with hundreds or thousands of terabytes in size) on cloud usually VMs are "tied" to a "family type" (the fact that I "want" 100TB of memory might end with a 1000 cores machne that I don't need and is too expensive).
In some cases, as mentioned by Dmitry, a specific DB would need 0% buffers (not to be cached at all) but other Db's that might be small (e.g. 100GB) might be accessed very often, hence need a 100% buffers availability.
Allocating X blocks of buffers to any Db can make wonders with performance (for systems that have complex datasets that are being mapped between many Db's).
@Yaron Munz, you have comments on your idea. Please answer them to help your idea to be promoted.
I have a scenario, where I would like to have something like this.
In a project, I have a lot of streams stored in the database, but the access speed to them is not critical. But, it eats too much memory in buffers, just because it's accessed and. So, it would be nice to be able to rate, how much of buffer can be used by this database, I would cut it to 0. So, only critical data would keep be stored in the buffer, even with less frequency of usage.
I am not sure i understand the issue you are trying to solve here.
IRIS/Cache caching is always trying to keep the latest accessed block in buffers, only removing the least used block if buffers are needed. So this sounds like you are trying to work around an environment that does not have suitable amount of memory available for the workload its used for. Else your highly accessed data will always stay in memory.