Kbase 63598: What is New in Progress OpenEdge 10.2B: Index Build
| Autor |
Tatiane Koslinsky - CAT |
| Acesso |
Público |
| Publicação |
26/09/2017 |
|
Some features were added to the indexing process when the service pack 5 was released.
The -TB parameter, which previously had a maximum value of 31, is now limited to 64. This parameter indicates the size of the block to sort data. Actually, the greater the better. This parameter with value 64 must speed up the indexing process.
The -TF parameter was created for Progress to load data to sort in the memory. It used to be on disk. Enter in the parameter the percentage of memory Progress can use to run the process. For example, -TF 90 indicates that Progress can use 90% of server memory. If the parameter is not specified, Progress automatically tries to use half the server's memory for the process.
Finally, the -rusage parameter reports statistics of the use of server resources at the end of the indexing process.
A test was carried out with a database of approximately 6 Gigabytes on a Linux 64 server with OpenEdge 10.2B02 64 bits. This database was indexed 3 times to establish the average indexing time of 233 seconds. Use the following command to index:
proutil hcm210a –C idxbuild all –TB 31 –TM 32 –SG 64 –spin 2000 –thread 1 –threadnum 4
After installing service pack 5, the database was indexed another 3 times, setting the average time of 201 seconds. New parameters were used this time. The command was:
proutil hcm210a –C idxbuild all –TB 64 –TF 90 –SG 64 –spin 2000 –thread 1 –threadnum 4
A gain of approximately 14% was set for this database.
Warning: There were more tests using the process statistics parameter (-rusage), and the average time skipped to 219 seconds.
Apparently, the bigger the database, the higher the percentage of gain, up to the memory limit of the server because data reading time on disk will not change. Time reduction is in the process of sorting the data in the memory, instead of the disk.