Replies: 1 comment
This premise is completely wrong. There is no difference in cache management between the modes. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Classic and SuperClassic has per connection page cache (
DefaultDbPageCache).SuperServer and SuperClassic has per database buffer for temp objects (
TempCacheLimit).If change
ServerMode, it requires change alsoDefaultDbPageCacheandTempCacheLimitand DPB for (many) aliases indatabases.conf.In addition, page cache for SuperServer must be recalculated into bytes based on page size of concrete database.
All this is inconvenient: the computer calculates, the human thinks. But not.
Suggestion.
Add two (per database) parameter:
PageCacheSize(bytes) andTempCacheSize(bytes).Classic shoud ignore new parameters at all.
SuperClassic should use TempCacheSize parameter value as value for TempCacheLimit and should ignore TCL from conf-files if both defined.
SuperServer should use both – TempCacheSize (as well as SuperClassic) and PageCacheSize and must recalculate PageCacheSize value from conf-files into DefaultDbPageCache before init of database page cache.
Thus, new parameters are "hidden" in runtime and will be used only as source values of the corresponding server parameters.
All reactions