Not all tables (entities) have the same level of importance when it comes to product performance. Some tables are critical, while others are less important to the overall transactional throughput. Likewise, disk storage solutions deliver varying levels of velocity and volume. You can save money and deliver better levels of performance by placing data where it is needed most.
The way to do this is to define storage groups for each I/O class of service (COS). The following table shows an example:
|
Class of service |
Service level |
Storage group |
Storage paths |
|
Critical |
.003 to .035 ms |
sg_critical |
/db/ts01, /db/ts02 |
|
Normal |
1 to 35 ms |
sg_normal |
/db/ts30, /db/ts31 |
|
Low |
No service level |
sg_low |
/db/ts50, /db/ts51 |
Placing tables into storage groups according to their importance can reduce disk storage...