Kbase P92875: Is there any performance impact when using database extent sizes more than 2GB?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/15/2010 |
|
Status: Verified
GOAL:
Is there any performance impact when using database extent sizes more than 2GB?
GOAL:
Does having larger extents make the database run slower?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
Generally, no.
The only time when you may experience a performance impact is if you are using manual file striping and you haven't spread the load across multiple disks very well.
For example. Say you have 3 hard drives (not hardware or software striped), have 3GB of data within your 6GB database structure, and you decide to have 3GB extent sizes. If you put the first extent on the 1st hard drive, the second extent on the 2nd hard drive, and bi file on the 3rd hard drive. All database reads and writes will be going to the 1st hard drive but the 2nd hard drive will not be utilized. This will have an obvious performance impact.
If you had 1.5GB extents with the second extent on the second hard drive, there would be 50% of your real data on the first hard drive and 50% on the second hard drive. Both hard drives will therefore be utilized.