Hi all, SQL Anywhere 12 WinHelp manual states
Now, a customer brought me to an interesting question: Does this only happen when starting the database together with a new server instance or does it also happen when a database that had been stopped before is restarted on a database server that been running meanwhile? And if so, does it make a difference if the running server had operated any other database(s) or just was idling with the virtual utility database? Could warming of a newly started database on an existing server replace cached pages from databases that have been operated before? TIA & Best Regards Volker Stoeffler Database Services Global CoE |
Cache Warming and Cache Collection is always performed whenever a database is started independent of how long the server has been running, except for these conditions:
I think your last question is asking if the cache warming process would cause existing database pages (from previously loaded/running databases on the server) that were already in the cache to be replaced? If this is the question then the answer is no. Cache warming will automatically stop if there are no free cache pages. Also note that cache warming will be stop if there is a significant amount of other IO (i.e. IO not associated with warming) occurring on the server. Therefore if a database is loaded on a server that has other database activity and that activity is requiring IO then it is likely that the newly loaded database will not be "completely" warmed (where "completely" means warmed to the same amount that it would be if the database was loaded on a newly started server). HTH Thank you very much Mark. This definitely answers my questions.
(20 Mar '13, 14:08)
Volker Stoef...
Replies hidden
(21 Mar '13, 06:49)
Volker Barth
2
@Mark: I'd suggest to add parts of your detailed explanation to the cited doc page, particularly the (limited) effect on already running databases on the same server - and that fact cache warming is generally not done for HA systems).
(21 Mar '13, 06:52)
Volker Barth
Replies hidden
|
Very interesting question, specially the last part!
I don't know (though the docs seem to imply it happens on database start, not on server start) - but allowing the according cache warming messages with "dbsrv12 -cv+" should tell you the truth anyway...