HP Cluster Test Software manual Cluster Test procedure as recommended by HP

Page 32

a.The auto Mem(GB) setting selects a memory size for each node that will accommodate the amount of memory available on that node. You may select an explicit size by clicking on the arrow adjacent to the Mem(GB) box. If you have more than one memory configuration in the cluster, select the one with lowest memory. For example, if one node in the cluster is configured with 8 GB and one with 16 GB, you should select 8 in the Mem(GB) box. When using the Cluster-wide option with Linpack, the Mem(GB) box will still be the amount of memory on each node – the values will be collected together to calculate how large the matrix should be for the whole cluster.

b.Next, select the percentage of total memory for the Linpack test by clicking on the arrow adjacent to the Mem% box. The default value is 80%. A Mem% value over 80% is likely to cause swapping or running out of memory.

c.Select Linpack to start the test.

d.Linpack running on individual nodes takes approximately one hour. The output of Linpack test is saved to files named HPL-node<x>where x is a node number. In this example, output is saved to files HPL-node0HPL-node76.

12.The final required test is Disk Test.

a.Enter the disk device (for example, /dev/sda) in the Device box. If nodes in the cluster have only one disk installed, you can select auto and let Disk Test figure out the device. You don’t need to change the % (percentage) parameter – the default value (10) is good. Do not run the test with more than 10% of the disk size because it will take a very long time to complete.

Time limits can be specified to control the amount of time that Disk Test runs.

When run with all, all-parallel, or all-sequential, Disk Test avoids testing physical disks and the logical volumes containing them.

b.Select Disk Test to begin the test.

NOTE: There is a known issue with Disk Test that causes Cluster Test to always indicate errors in Disk Test’s standard error output. As long as the Disk Test .err file in the logs directory only lists the node names of the systems tested with Disk Test, this error can be ignored.

c.If you want to save your test results to a file, select Save Log. To clear the output window, select Clear Log.

13.Remember to run a Hardware Inventory (Tools→Hardware Inventory from the Cluster Test toolbar) to check and save the cluster hardware configuration. See “Hardware Inventory” (page 36) for more information.

14.When all the testing is complete, uninstall Cluster Test and remove all associated log, error, and script files. Refer to the HP Cluster Test Installation Guide, available at http://www.hp.com/ go/ct-docs, for the appropriate uninstall instructions for Cluster Test.

32 Cluster Test procedure as recommended by HP

Image 32
Contents HP Cluster Test Administration Guide January Contents Documentation feedback Glossary Index Useful files and directories Utility commandsSample test output CT Image CT Image using a networkVarieties of Cluster Test RPM Cluster Test GUI Starting Cluster TestFiles generated by Cluster Test Running cluster testsCluster Test GUI Running cluster tests Configuration settings Running tests in a batch Using scripts to run tests Running cluster tests Test descriptions CrissCrossMonitoring tests and viewing results Nodes monitoring windowTest output window Monitoring tests and viewing results Performance analysis Test report Checking the InfiniBand fabric Cluster Test toolbar menus Cluster Test toolbar menusFiles generated by accelerator test Accelerator test GUIStarting accelerator tests Verify Running accelerator testsGPU detection Sgemm Single Precision General Matrix Multiply Test Dgemm Double Precision General Matrix Multiply TestBandWidth GPU Bandwidth Test Memory TestNvidia Linpack Cuda Accelerated Linpack Benchmark Additional software Cluster Test procedure as recommended by HPConfiguring Cluster Test when using RPM Accelerator test procedure Cluster Test procedure as recommended by HP Cluster Test procedure # checkadm Cluster Test procedure Cluster Test procedure as recommended by HP Performance monitor Performance monitor utilityPerformance Monitor toolbar menu Xperf utility Firmware Summary Cluster Test toolsHardware Inventory Server health check Excluding the head node from tests Disk Scrubber Cluster Test tools Running tests in parallel An example cloned per-node directory Creating and changing per node filesAn example per-node directory NFS performance tuning NfsTroubleshooting Detecting new hardwareTroubleshooting Cluster Test Cluster Test Troubleshooting GuideSupport and other resources Scope of this documentIntended audience Contacting HPNew and changed information in this edition Related informationDocumentation WebsitesTypographic conventions Customer self repairCustomer self repair Useful files and directories Cluster Test Useful Files and DirectoriesUtility commands AnalyzeConrep Files generated by ibfabriccheck Inspectibfabric.pl Inspectibfabric.pl Utility commands Ipmitool Pdsh Sample test output CrissCrossSample test output Test4 Pallas Mpibyte Sample test output Stream Node24 Triad 3078.7949 3355 3488 3536 Disk Test CPULinpack UTKPassed Passed Passed Documentation feedback Glossary CMUIndex MPI Accelerator
Related manuals
Manual 25 pages 60.17 Kb