R710 SqL virtualization

9 install windows updates net 20 framework and

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: ettings for the Network installation. 8. Type Workgroup for the workgroup. 9. Install Windows Updates, .NET 2.0 framework, and DVDStore client executable DVD Store setup Data generation overview We built the database schema using the scripts in the DS2 distribution package, though we made a few minor modifications. The DS2 stress tool provides options to generate 10MB, 1GB, or 100GB datasets. To get the tool to generate the 20 GB of user data we used in this test, we had to make a few straightforward changes to the source code and to the DVD Store application’s scripts. Note: We created our test data on a Linux system to take advantage of the larger RAND MAX. Editing the ds2_create_orders.c module The module ds2_create_orders.c defines constants that define the maximum values for the customer ID and the product ID. The constants for the 20GB database size did not exist. We added the constants for this size. On the command line for the ds2_create_orders.c module, we specified the size. The available options were S (small), M (medium), and L (large). We added the case W for the 20GB database. In the switch statement that sets the values for the variables max_cust_id and max_prod_id, we added cases that assigned them the proper values for the 20GB database size. We recompiled the ds2_create_orders.c module on Linux, following the instructions in the header comments. We used the following command line: gcc –o ds2_create_orders ds2_create_orders.c –lm Editing the ds2_create_cust.c module We had to make the same changes to the ds2_create_cust.c module that we made to the ds2_create_orders.c module. On the command line for the ds2_create_cust.c module, we specified the size. The available options were S (small), M (medium), and L (large). We added the case W for the 20GB database. In the switch statement Principled Technologies, Inc.: Virtualized OLTP workload performance comparison of end-to-end solutions: Dell PowerEdge R710 with Dell EqualLogic storage vs. HP ProLiant DL385 G5 with HP StorageWorks EVA 4400 storage 14 that sets the values for the variables max_cust_id and max_prod_id, we added cases that assigned them the proper values for the 20 GB database size. We recompiled the ds2_create_cust.c module on Linux, following the instructions in the header comments. We used the following command line: gcc –o ds2_create_cust ds2_create_cust.c –lm Generating the data for the 20GB database We used shell scripts to run all four of the executables that generate the data. The distribution did not include shell scripts for the 20GB size. We wrote shell scripts based on the ds2_create_cust_large.sh and ds2_create_orders_large.sh scripts. The ds2_create_prod and ds2_create_inv executables did not ship with associated shell scripts, so we created shell scripts using the instructions in the readme files. We ran the shell scripts in the following order to generate the data for the 20GB database: 1. 2. 3. 4. ds2_create_orders_20gb.sh ds2_create_inv_20gb.sh ds2_create_prod_20gb.sh ds2_create_cust...
View Full Document

Ask a homework question - tutors are online