HP ProLiant 3000 DSS Sizing and Tuning of Oracle8 for Windows NT on Compaq Ser - Page 25

DSS Sizing and Tuning of Oracle8 for Windows NT on CompaqServers Page 23 NOTE: There is a constraint in Oracle8 memory usage which prohibits the Oracle process from using all 3GB of virtual address space. Figure 13: Compaq ProLiant 6500, 1M cache (3G, 2G, 1G, 512M RAM) - TPCD Query Times ProLiant 6500, 1M cache 800 700 600 500 400 300 3G 2G 1G RAM 512M Figure 14: Compaq ProLiant 6500, 1M cache (3G, 2G, 1G, 512M RAM) - Selected TPCD query data. Query time in seconds. Query # 5 7 9 11a 13 15b 17 3G 2152.47 1196.1 3492.87 171.31 3.59 225.93 16.2 2G 2158.85 1217.14 3456.51 169.17 3.67 225.51 16.42 1G 2291.47 1272.26 4024.89 168.71 16.63 225.09 16.46 512M 4599.31 5244.27 17112.15 403.74 91.74 224.94 225.4 In figure 11, assuming that you are cost bound, configuring the Compaq ProLiant 6500 with 1G RAM seems to be optimal. However, if you look at figure 12, you can see that the addition of RAM does not help all queries. Thus, it is also important to look at query definitions and functionality in determining the amount of RAM you need. The following gives explanation of memory usage for TPC-D queries identified in figure 12. The TPC-D schema and SQL code for these queries are included in Appendix A (schema) and Appendix C (SQL code). Both queries 5 and 13 have a small return set (less than or equal to seven rows), but require a join of the largest tables in the database. Utilizing 512M and 1G RAM, queries 5 and 13 do not have enough memory to perform optimal joins. Looking at figure 12, you can see that 2G RAM provides enough memory for both joins. Query 7's performance improves with the addition of RAM up to 3G, so 3G RAM is a viable configuration. This indicates that the additional memory helps in the 6-table join and the storage © 1998 Compaq Computer Corporation, All Rights Reserved Doc No ECG156/0398