There is the following dbeng12/dbsrv12 server option:
Suppose, for example, my database has the following size: 'FileSize' * 'PageSize' = 4 004 655 104
SQL Anywhere Network Server Version 18.104.22.16867 4194304K of memory used for caching Minimum cache size: 4194304K, maximum cache size: 7529760K OS Available: 5027080K, Working Set: 151020K, Cache Target: 4069273K, Cached: 96% OS Available: 5026052K, Working Set: 151420K, Cache Target: 4069330K, Cached: 96% OS Available: 5025552K, Working Set: 151596K, Cache Target: 4069426K, Cached: 96% ...
But, if Start line = C:\Program Files\SQL Anywhere 12\bin64\dbsrv12.exe -c 3G -cs
SQL Anywhere Network Server Version 22.214.171.12467 3145728K of memory used for caching Minimum cache size: 3145728K, maximum cache size: 7529760K ...
And if I just increase the size of the database file:
ALTER DBSPACE system ADD 2 GB; /*('FileSize' * 'PageSize' = 6 152 138 752 and ('FileSize' - 'FreePages') * 'PageSize' = 3 980 476 416) */
the information about the cache no longer appear after reloading the server for -c 4G (or 5G):
SQL Anywhere Network Server Version 126.96.36.19967 5242880K of memory used for caching Minimum cache size: 5242880K, maximum cache size: 7529760K ...
There are a few cases where it won't display information where, perhaps, it could. Generally speaking, no message is displayed whenever neither growing nor shrinking the cache is possible/reasonable. In the cases you've shown, shrinking isn't an option because you are already at the minimum cache size. Growing isn't an option in some of the cases shown because the cache is larger than then entire database file (plus heap plus temp file): since everything can be cached, there's no point in growing. Growing also isn't an option if there have been no cache replacements yet or a few other criteria that likely are not relevant here.
answered 24 Jan '14, 13:07