Migrating Enterprise Databases from Sun Servers to Dell 8G Servers

Transcription

1 Migrating Enterprise Databases from Sun Servers to Dell 8G Servers Part 1: The PowerEdge 2850 Running Windows Server 2003 Enterprise Product Group (EPG) Dell White Paper By Todd Muirhead and Dave Jaffe November 2004

2 Contents Executive Summary... 3 Introduction... 4 The Hardware... 5 Database Setup and Migration... 7 The Application... 9 The Database Schema... 9 The Stored Procedures The Online Transaction Processing Driver Application Results Conclusions Acknowledgements Appendix A. Purchase Stored Procedure Tables Table 1: Comparison of Sun Fire V440 vs the Dell PowerEdge Table 2: Dell/EMC Storage... 6 Table 3: Database Initialization Parameters... 8 Table 4: Database Tablespaces... 8 Table 5: DVD Store Database Schema... 9 Table 6: OLTP Driver Parameters Table 7: Results November 2004 Page 2 Dell Enterprise Product Group

3 Section 1 Executive Summary As industry standard Intel-based servers from Dell continue to improve in performance and value, customers are migrating their mission critical applications from proprietary Unix based systems. The latest generation of Dell s servers continues the trend of increasing performance and value by utilizing Intel s Xeon processor with EM64T technology and the latest server hardware architecture features. To demonstrate the value and benefits of Dell s latest generation of servers, a Dell PowerEdge 2850 with dual 3.4 GHz Xeon processors was installed with Microsoft Windows Server 2003 and an enterprise database manager and used as a target platform for a migration from a Unix server from Sun Microsystems Inc., a Sun Fire V440 with four 1.28 GHz UltraSPARC IIIi processors. Using tools provided with the database manager software, a large (100 GB) database representing an online store was easily moved from the Sun server to the Dell server. The online store running on the Dell PowerEdge 2850 with dual 3.4 GHz Xeon processors was able to handle 77% more orders per minute than the Sun Fire V440, and was 49% less expensive than the Sun system. November 2004 Page 3 Dell Enterprise Product Group

4 Section 2 Introduction Previous studies in this series have shown the advantages of migrating large databases from proprietary Unix/RISC platforms such as the Sun Fire V440 from Sun Microsystems Inc. to industry standard servers from Dell such as the PowerEdge way Xeon Processor MP system. A study of migration from the Sun Fire V440 to the PowerEdge 6650 running Windows Server 2003 is available at SunV440-PE6650-W2K3.pdf; migration to the PowerEdge 6650 running Red Hat Enterprise Linux 3 is at PE6650-RHEL3.pdf. In this study, conducted by Dell in November 2004, the Sun Fire V440 with four 1.28 GHz UltraSPARC IIIi processors was compared to the new Dell PowerEdge 2850, one of Dell s new Eighth Generation (8G) servers utilizing Intel s Xeon processor with EM64T technology. EM64T technology enables enterprises to use 32-bit versions of their critical software like database managements systems now and to upgrade to 64-bit versions when they become available in the near future. With two Xeon processors running at speeds as fast as 3.6 GHz, an 800 MHz Front Side Bus and up to 12 GB of DDR2-400 memory, the PowerEdge 2850 offers excellent server performance in a two-rack unit (2U or 3.5 ) server. To demonstrate the ease and potential benefits of migration from Sun servers running Solaris, a large (100 GB) database running on a leading enterprise database manager was quickly and easily moved from a Sun Fire V440 4-way server to the Dell PowerEdge way server. No data was lost during the migration, and the application (an online DVD store) ran 77% faster on the PowerEdge 2850 than on the Sun Fire V440.The PowerEdge 2850 was equipped with 8GB of memory and two 3.4 GHz Xeon processors, a notch slower than the fastest processors available for the system. Similarly, the Sun Fire V440 configuration used in this test, with four 1.28 GHz UltraSPARC IIIi processors and 8 GB of memory, is classified by Sun on their web site ( uct_cp&catid=104994) as the Medium Sun Fire V440 configuration, with the processor speed being slightly slower than the fastest UltraSPARC IIIi processor available at the time, GHz. 1 The Sun and Dell hardware used in these tests is described in the next section, followed by a description of the database setup and how it was migrated from the Sun server to the Dell server in Section 4. The DVD store application is described in detail in Section 5, along with details on the tests performed. Results are shown in Section 6. November 2004 Page 4 Dell Enterprise Product Group

5 Section 3 The Hardware This study involved migrating a large (100 GB) database from a 4-processor system, the Sun Fire V440, to a Dell 2-processor system, the PowerEdge The processors used for both systems were not the fastest speed offered by each vendor at the time of the tests (Nov. 2004) four 1.28 GHz/1 MB L2 cache Ultra SPARC IIIi processors in the Sun Fire V440 and two 3.4 GHz / 1 MB L2 cache Xeon processors in the Dell PowerEdge 2850, both servers with 8 GB of memory. 1 Details are shown in Table 1. Operating System CPU Sun Fire V440 Dell PowerEdge 2850 Solaris 9 12/03 4x 1.28 GHz UltraSPARC IIIi w/ 1MB L2 cache Microsoft Windows Server 2003 Enterprise Edition 2x 3.4 GHz/1 MB L2 Cache Xeon Memory 8 GB 8 GB (4 x 2 GB DIMMs) Internal Disks NICs 4x 73 GB 10K RPM Ultra320 SCSI 2x 10/100/ Mb/s (Internal) 2x 73 GB 10K RPM Ultra320 SCSI 2x 10/100/ Mb/s (Internal) Disk Controller On-board SCSI PERC 4ei Fiber Channel HBA Remote Management Service Hardware Price (without HBAs) Price of Database Licenses ($15,000/CPU) 2x QLA x QLA 2340 Serial Management Card 3-Year Gold Support w/ 7x24 Onsite $27,339 $14,817 $60,000 $30,000 Total Price $87,339 $44,817 Source 11/29/04 Dell Remote Access Card, Version IV, without Modem 3-Year Gold Support w/ 7x24 Onsite /29/04 Table 1: Comparison of Sun Fire V440 vs the Dell PowerEdge 2850 November 2004 Page 5 Dell Enterprise Product Group

6 List prices of the two systems are shown in Table 1. The list price of the database manager license, based on processor count, is included in the calculation of the total price and is shown in the table. The operating system cost is included in the server hardware price. Pricing of the configurations did not include the SAN hardware or software. Microsoft Windows Server 2003 Enterprise Edition was installed on the Dell PowerEdge 2850 and Solaris 9 12/03 was installed on the Sun Fire V440. The Sun Fire V440 uses a 64-bit architecture which allows a flat addressing model to address the entire 8 GB of memory installed in the server directly. The 32-bit architecture of the Dell 2850 requires some additional parameters to enable access to the full 8 GB. The /3GB and /PAE parameters were added to the Windows boot.ini to enable the additional memory support in Windows. These will not be needed when 64-bit Windows Server 2003 and 64-bit database software are available for the EM64T processor. Storage for both the Dell and Sun servers was provided by a Storage Area Network (SAN)-attached Dell/EMC CX700 fibre channel storage array. Each server was attached to the SAN via two QLogic Host Bus Adapters. Each server was assigned to a set of storage logical units (LUNs) that used the same number and type of disk drives. The EMC compatibility matrix (available at which includes both the Dell PowerEdge 2850 and Sun Fire V440, was consulted to ensure that the proper versions of drivers and firmware were utilized on both the Dell and Sun servers. The version of the QLogic 2340 driver for Windows and PowerPath for Windows were both installed on the Dell systems. PowerPath for Solaris and QLogic driver version 4.13 for Solaris were installed on the Sun Fire V440 server. PowerPath provides load-balancing and failover for the dual HBAs that were present in all systems. The storage components used for both servers in the test are shown in Table 2. Controller Disk Enclosures Disks LUNs Software 1 Dell/EMC CX700 3 Dell/EMC DAE2 40 x 73 GB/ 10K RPM 3 10-Disk RAID 1/0 LUNs for Data 2 2-Disk RAID 1 LUN for Logs 1 5-Disk RAID 0 for Temporary Data Staging for Loading 1 HotSpare Disk Navisphere Manager Access Logix PowerPath Table 2: Dell/EMC Storage November 2004 Page 6 Dell Enterprise Product Group

7 Section 4 Database Setup and Migration A leading enterprise database server was installed and configured on the Sun Fire V440 server and the Dell PowerEdge 2850 server. Installation and configuration of the database software were done according to the database provider s installation guide for the respective server platforms. The enterprise database server used provides the same Java-based tool for installation on both Solaris and Windows allowing for the exact same options to be selected. A database creation assistant wizard was used on the Sun Fire V440 server to create the initial database instance. Scripts were then used to finish the creation and loading of the test database. The database used consisted of approximately 100 GB worth of data, indexes, and stored procedures. The 100 GB database was migrated from the Sun Fire V440 server to the Dell PowerEdge 2850 server using migration tools included with the database server. Using a few commands, the Sun data files were converted and then transported from the 64-bit Solaris-based server to the 32-bit Windows-based server. The basic steps were to create copies of the data files on the Sun server, convert the copies into a Windows-readable format, move the newly created files over to the Dell server, and then connect the transported data files into the database instance running on the Dell server. Database initialization parameters were obtained by allowing the database to run in an auto-tuning mode on the Sun Fire V440. A target of 7 GB of RAM was established for the auto-tuning of the database to work with. After allowing the auto-tuning to occur on the Sun server, the tuned settings were applied to the target Windows system as closely as possible. There were some slight differences in the memory initialization parameters due to the different memory models on the different platforms. Specifically, the database initialization parameters USE_INDIRECT_DATA_BUFFERS and DB_BLOCK_BUFFERS are used instead of DB_CACHE_SIZE to specify the amount of memory to be used. A slightly larger amount of memory was usable by the database on the V440 due to a small amount of memory that must be used on the PowerEdge 2850 to enable the very large memory support on the 32-bit platform (the Sun s System Global Area was 6.84 GB, compared to 6.78 GB on the Dell system). The nondefault database initialization parameters that were used are listed in Table 3. November 2004 Page 7 Dell Enterprise Product Group

8 Parameter Sun Fire V440 Dell PowerEdge 2850 DB_BLOCK_BUFFERS DB_BLOCK_SIZE DB_CACHE_SIZE JAVA_POOL_SIZE LARGE_POOL_SIZE OPEN_CURSORS PROCESSES PGA_AGGREGATE_TARGET SHARED_POOL_SIZE SORT_AREA_SIZE UNDO_RETENTION USE_INDIRECT_DATA_BUFFERS TRUE Table 3: Database Initialization Parameters Both systems used the database-provided storage manager for the database data files and log files. This storage manager reduces the overhead of a file system by allowing the database to access and manage the storage more directly. The database tablespaces were set up exactly the same on each of the systems (see Table 4). The three RAID 1/0 ten-drive LUNs were put into one disk group in the storage manager which was used for the data, index, undo and temporary tablespaces. Each of the two RAID 1 LUNs was assigned to its own disk group and used for redo logs. Tablespace Contains Space Used/Available CUSTTBS Customer Table 47 GB / 50 GB INDXTBS Indexes 24 GB / 30 GB ORDERTBS DS_MISC Orders and Orderlines Tables Product and Categories Tables 25 GB / 30 GB 0.09 GB / 0.5 GB UNDOTBS Undo Tablespace 0.07 GB / 3 GB TEMP Temporary Table 18 GB / 18 GB Table 4: Database Tablespaces November 2004 Page 8 Dell Enterprise Product Group

9 Section 5 The Application The test used the same version of the online DVD store database application employed in the previous Red Hat Linux migration study referred to in the Introduction. This version of the database application includes the use of advanced database features such as transactions, triggers and referential integrity constraints. In addition, functionality typical of some online stores is included, including reporting to the user previous purchases and recommendation of titles enjoyed by others. This version is referred to as DVD Store 2 or DS2. The database (100 GB total size), representing an online DVD store with 1 million DVD titles, was driven by a ProC-language program simulating users logging in to the online store, browsing for DVDs by title, author or category, and then finally submitting an order. The driver program measures the number of orders per minute that the database can handle as well as the total response time as seen by the simulated end users. The Database Schema The DVD store was comprised of five main tables and one other (see Table 5). Table Columns Number of Rows Customers Orders CUSTOMERID, FIRSTNAME, LASTNAME, ADDRESS1, ADDRESS2, CITY, STATE, ZIP, COUNTRY, REGION, , PHONE, CREDITCARD, CREDITCARDEXPIRATION, USERNAME, PASSWORD, AGE, INCOME, GENDER, PROD_ID_IDX, PROD_ID1, PROD_ID2 PROD_ID10 ORDERID, ORDERDATE, CUSTOMERID, NETAMOUNT, TAX, TOTALAMOUNT 200 million 120 million Orderlines ORDERLINEID, ORDERID, PROD_ID, QUANTITY, ORDERDATE 600 million Products Reorder PROD_ID, CATEGORY, TITLE, ACTOR, PRICE, QUAN_IN_STOCK, SPECIAL, COMMON_PROD_ID1, COMMON_RATING1, COMMON_PROD_ID2, COMMON_RATING2, COMMON_PROD_ID3, COMMON_RATING3, SALES PROD_ID, DATE_LOW, QUAN_LOW, DATE_REORDERED, QUAN_REORDERED, DATE_EXPECTED Categories CATEGORY, CATEGORYNAME 16 1 million variable Table 5: DVD Store Database Schema November 2004 Page 9 Dell Enterprise Product Group

10 The Customers table was pre-populated with two hundred million customers, one hundred million US customers and one hundred million customers from the rest of the world. The Orders table was pre-populated with ten million orders per month for a full year. The Orderlines table was pre-populated with an average of 5 items per order. The Products table contained one million DVD titles. New in DS2 is the Reorder table. When the QUAN_IN_STOCK value for each product in the Products table falls below a specified value, a trigger is set off which calls code to write information about the product to the Reorder table. A separate process (not modeled) would watch this table to initiate reordering of needed titles. Finally, the Categories table listed the 16 DVD categories. The Stored Procedures The DVD Store database was managed through six stored procedures. The first two were used during the login phase. If the customer was a returning customer, Login was used to retrieve the customer s information, in particular the CUSTOMERID. If the customer was a new customer, New_customer was used to create a new row in the Customers table with the user s data. Following the login phase the customer might search for a DVD by category, actor or title. These were implemented by Browse_by_category, Browse_by_actor and Browse_by_title, respectively. Finally, after the user had made his or her selections, the Purchase stored procedure (Appendix A) was called to complete the transaction. The stored procedures of the DS2 application have features to better model today s online stores. During Login, for example, the user s previous order (up to ten titles) is reported, along with titles that other customers who like those titles have recommended. The Browse_by_category returns those titles in the specified category that are currently on sale. And the Purchase stored procedure now checks the QUAN_IN_STOCK field from the Products table to see if a title is available. This is done using a database transaction, so that if there is insufficient quantity to fill the order neither the QUAN_IN_STOCK data is updated nor is a new record written to the ORDERS table. The Online Transaction Processing Driver Application A multi-threaded driver program was written to model an order entry or online transaction processing (OLTP) workload. Each thread of the OLTP driver application connected to the database and made a series of stored procedure calls that simulated users logging in, browsing and purchasing. Since there were no simulated user think times or key times, the database connections were kept full, simulating what happens in a real multi-tiered application where some small number of connections are pooled and shared among the web servers that may be handling thousands of simultaneous customers. Thus a realistic simulation of database activity was achieved without needing to model thousands of users. Each thread of the OLTP driver modeled a series of customers going through the entire sequence of logging in, browsing the catalog several ways and finally purchasing the selected items. Each completed sequence by a customer counted November 2004 Page 10 Dell Enterprise Product Group

11 as a single order. The driver measured order rates and the average response time to complete each order. Several tunable parameters were used to control the application and are described in Table 6. Parameter Description Value(s) used in test n_threads Number of simultaneous connections to the database See Table 7 warmup_time Warmup time before statistics are kept 1 min run_time Run time during which statistics are kept varied pct_returning Percent of users that are returning users 80% pct_new Percent of users that are new users 20% n_browse_category Number of searches based on category Range: 1-3 Average: 2 n_browse_actor Number of searches based on actor Range: 1-3 Average: 2 n_browse_title Number of searches based on title Range: 1-3 Average: 2 n_line_items Number of items purchased Range: 1 9 Average: 5 net_amount Total amount of purchase Range: $ $ Average: $ Table 6: OLTP Driver Parameters November 2004 Page 11 Dell Enterprise Product Group

12 Section 6 Results The DVD store database running on the Sun Fire V440 was tested using the driver program described in the previous section. The database was then migrated over to the Dell PowerEdge 2850, where it was tested with the same driver program. The tests measured how many orders per minute each database server could handle, while keeping each server s CPU (central processor unit) utilization about 90%, a typical system target to allow headroom for order spikes. CPU utilization was measured using the vmstat program under Solaris and the Performance Monitor program under Windows 2003 Server. As seen in Table 7, the Dell PowerEdge 2850, with two 3.4 GHz processors, while priced 49% less than the Sun Fire V440 (total server hardware and software price, including OS), could handle 77% more orders per minute. In terms of price/performance the Sun Fire V440 costs $10.81 per order per minute whereas the Dell Power Edge 2850 costs $3.14 per order per minute. In other words, the Sun Fire V440 cost over 3 times or 244% more than the Power Edge 2850 per unit of work it could handle. System Sun Fire V440 4x1.28 GHz/1 MB L2 Cache Dell PowerEdge x 3.4 GHz/1 MB L3 Cache Simultaneous Database Connections Orders Per Minute (larger is better) Average Response Time (s) CPU Utilization % Dell PE2850 Performance Advantage Over Sun Fire V440 Total Hardware + Software Price Price/ Performance ($/OPM) Dell Price/Perf Advantage $87,339 $ , x $44,817 $ % Table 7: Results November 2004 Page 12 Dell Enterprise Product Group

13 Section 7 Conclusions To demonstrate the ease and benefits of migrating enterprise applications from proprietary Unix servers to industry standard Intel-based servers, a large (100 GB) database built with a leading enterprise database server was easily migrated from a Sun Fire V440 4-way server configured with 1.28 GHz/1 MB L2 UltraSPARC IIIi processors and 8 GB of memory to a Dell PowerEdge way server configured with the next-to-fastest processors available (3.4 GHz/1 MB L2 cache Xeon processors) and 8GB of memory. 1 The PowerEdge 2850 with the 3.4 GHz processors was 77% faster than the Sun Fire V440 and 49% less expensive, a price/performance advantage of 244%. While the Sun SPARC architecture currently supports 64-bit operating systems and applications, the Intel Xeon with EM64T technology shipping in Dell s Eighth Generation servers like the PowerEdge 2850 will support 64-bit Windows 2003 Server and applications when the software ships in the coming year, while supporting all of today s 32-bit software. THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND. 1 The Sun Fire V440 offered two processor speeds at the time of testing: 1.28 GHz and GHz. The PowerEdge 2850 offered 5 processor speeds, with the fastest being 3.6 GHz and the slowest, 2.8 GHz. Dell expects server testing performance to vary with processor speed. 2 This term does not connote an actual operating speed of 1 Gb/sec. For high speed transmission, connection to a Gigabit Ethernet server and network infrastructure is required. 3 Service may be provided by third-party. Technician will be dispatched if necessary following phone-based troubleshooting. Subject to parts availability, geographical restrictions and terms of service contract. Service timing dependent upon time of day call placed to Dell. U.S. only. Dell and PowerEdge are trademarks of Dell Inc. EMC, Navisphere and PowerPath are registered trademarks and Access Logix is a trademark of EMC Corp. Intel and Xeon are registered trademark of Intel Corp. Red Hat is a registered trademark of Red Hat Inc. Linux is a registered trademark of Linus Torvalds. Microsoft and Windows are registered trademarks of Microsoft Corporation. Sun and Solaris are registered trademarks of Sun Microsystems, Inc. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims proprietary interest in the marks and names of others. Copyright 2004 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the express written permission of Dell Inc. is strictly forbidden. For more information, contact Dell. Information in this document is subject to change without notice. November 2004 Page 13 Dell Enterprise Product Group

14 Section 8 Acknowledgements The authors would like to thank Terri Mirka for supporting the funding of the Sun Fire V440 and the Oracle Alliance team (James Jech, Patrick Hannan and John Von Voros) for their support of this work. November 2004 Page 14 Dell Enterprise Product Group

15 Appendix A. Purchase Stored Procedure -- copyright Dell Inc CREATE OR REPLACE PROCEDURE "DS"."PURCHASE" ( customerid_in INTEGER, number_items INTEGER, prod_id_in DS_TYPES.N_TYPE, qty_in DS_TYPES.N_TYPE, netamount_in NUMBER, taxamount_in NUMBER, totalamount_in NUMBER ) AS date_in DATE; neworderid INTEGER; item_id INTEGER; BEGIN SELECT ORDERID_SEQ.NEXTVAL INTO neworderid FROM DUAL; --date_in := SYSDATE; date_in := TO_DATE('2003/10/31', 'YYYY/MM/DD'); -- CREATE NEW ENTRY IN ORDERS TABLE INSERT INTO ORDERS ( ORDERID, ORDERDATE, CUSTOMERID, NETAMOUNT, TAX, TOTALAMOUNT ) VALUES ( neworderid, date_in, customerid_in, netamount_in, taxamount_in, totalamount_in ) ; -- ADD LINE ITEMS TO ORDERLINES FOR item_id IN 1..number_items LOOP INSERT INTO ORDERLINES ( ORDERLINEID, ORDERID, PROD_ID, QUANTITY, ORDERDATE ) VALUES ( item_id, neworderid, prod_id_in(item_id), qty_in(item_id), date_in ) ; END LOOP; END PURCHASE; November 2004 Page 15 Dell Enterprise Product Group