Hi
I'm trying to tune access times on a table which size might vary (from 0
to at least several thousand records).
I've tried marking this table 'volatile' but it caused performance
penalties on some operations:
- table scan from 10 to 200 timerons
- index scan from 15 to 500 timerons
(I took those times from access plans as explained by DB2)
I understand that when a table is marked 'volatile' the optimizer
prefers index scans before table scans, but why on earth does the same
operation takes much more time after the change ?
Or maybe this performance penalty is small and I should not care about
it? I predict that the maximum size of the table might be about 20 000
records.
Thanks in advance
--
Szymon Dembek