|
feijizjh, I said queries only. If you have deletes and updates, just run queries against the tables the deletes and updates reference. If you really want, you can also run the deletes and updates and immediately rollback. You didn't seem to get the point. The point is to bring the blocks into buffer cache. We don't care what the actual SQLs are like. If you have too many SQLs, just pick a few tables that are referenced often in those SQLs.
viadeazhu, I agree it's a good idea to let the app warm up the buffer cache. The great philosopher Zhuang Zi said "Do nothing and nothing is left undone!" But it's possible that the users expect to come to office in the morning and start to work expecting immediate response even at the beginning. If so, DBAs can do something to make them happier. Otherwise, hire a low-wage secretary to go through some typical screens of the app very early in the morning, before the VIP users come in. Otherwise, just configure keep cache and throw frequently used tables into it.
Before we make such suggestions, can we make sure the frequently run SQLs are all tuned?
Yong Huang |
|