Kbase 11242: Use of Sort -TB and -TM on PROUTIL idxbuild - Index Rebuild
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/12/2009 |
|
Status: Verified
GOAL:
What effect do the -TB and -TM startup parameters have on the Progress PROUTIL idxbuild utility?
GOAL:
How to Improve idxbuild performance?
FACT(s) (Environment):
Progress 6.x
Progress 7.x
Progress 8.x
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
When you answer "yes" to sorting for an index rebuild, the blocks are put into a sort file and then moved back several at a (-TM) time. This provides the following benefits:
- The blocks in the database are closer together.
- Progress can regulate how full the blocks are.
- The speed of both retrieval and insertion of records is
increased as well as the speed of the index rebuild itself.
A non-sorted index rebuild replaces the index records in the same way a regular insert is done into the database, complete with block splits and empty spaces. A non-sorted index rebuild can help but not nearly as much as one done with sorting.
Both parameters have the same effect on index corruption (fixes) but, as stated above, a sorted index rebuild should be better for performance reasons.
Use of the -TB option with the index rebuild utility improves performance at the cost of disk space while use of the -TM option improves performance at the cost of memory usage. Both -TB and -TM have default values of 2 and 5 and maximum values of 31 and 32. Using multiples of 8, -TM should be set to 24, not 31.
The parameters are specified as:
proutil <dbname> -C idxbuild -TB 24 -TM 32