Performance recommendations graveyard
You can review the performance recommendations that were deprecated by this release.
| Deprecated In | Deprecated Recommendations | Comments |
|---|---|---|
| Sterling Order Management System Software 8.0 | Removed recommendations on how to diagnose and tune JVM fragmentation. | The JVM was redesigned to eliminate fragmentation issues. |
| Sterling Supply Chain Applications 7.9 | Removed setting specific values for Db2® LOCKLIST, MAXLOCKS, PCKCACHESZ, SHEAPTHRES_SHR, SORTHEAP, NUM_IOCLEANERS, NUM_IOSERVERS, DFT_PREFETCH_SZ, MAXAPPLS and AVG_APPLS. | Rather than specifying specific values, we recommend allowing Db2 to automatically manage these parameters. |
| Sterling Supply Chain Applications 7.9 | Oracle cursor_sharing=SIMILAR | Use cursor_sharing=FORCE. |
| Yantra 7x, 7.7 in Oracle10g | Oracle Parameters - shared_pool_size | Use Oracle10g/11g Automatic Memory Management (AMM) sga_max_size, sga_target and pga_aggregate_target. |
| Yantra 7x, 7.7 in Oracle10g | Statistics gathering | Oracle10g/11g automatically schedules statistics gathering during its maintenance window. See new recommendations in Index and table statistics |
| Yantra 7x, 7.5 and Oracle10g RAC | In the past, we adhered to Oracle's recommended setting for max_commit_propagation_delay of 700 centiseconds (or 7 seconds). Oracle has revised its recommendation to 0 effectively disabling the Lamport scheme. | For existing Oracle instances, reset max_commit_propagation_delay so that the default value is 0. |