White Papers
Table Of Contents
- 1 Introduction
- 2 Generic Recommendations
- 3 Test Environment and Methodology
- 4 Scalability and Performance tests for Power Manager 2.0
- 5 Addition of devices and groups in Power Manager
- 6 Metric Collection
- 7 Power Policy (Power Capping)
- 8 Emergency Power Reduction
- 9 Alert Thresholds
- 10 Importing Physical Groups and Device Association from a CSV file
- 11 Plugin Actions (Install, Disable, Enable, Uninstall)
- 12 Longevity Test Results
- 13 Troubleshooting
- 14 Conclusion
- 15 Technical Support and Resources.
Generic Recommendations
7 Benchmark the Performance, Reliability and Scalability of Dell EMC OpenManage Enterprise Power Manager
2.0 in Data Center Environment
2 Generic Recommendations
Power Manager features are similar to OpenManage Enterprise that are dependent on the underlying
hardware configurations and the resources allocated to the hosted Virtual Machine. To optimize the setup and
task scheduling in Power Manager, prioritize the hardware allocation using the following guidelines:
Memory:
Memory is a gating factor to a number of tasks which can be run simultaneously. It is recommended to
manually increase the RAM from default value while running a maximum scaled configuration to allow more
concurrent processes. 16GB RAM is the minimum requirement for Small scale deployments whereas 32GB is
the minimum requirement for Enterprise scale deployments.
CPU:
Power Manager leverages the services from OpenManage Enterprise for running multiple tasks by using
different threads concurrently. It is recommended to add more cores for better performance since few of the
database operations in Power Manager are CPU intensive. Increased hardware specifications, processor
cores, and RAM yield to a better performance than what is detailed in this document. For Small Deployments,
the minimum processor requirement is 4 cores whereas for Enterprise Deployments, the minimum
requirement is 8 cores.
Network Bandwidth:
Majority of the features in Power Manager are based on network interactions between the appliance and
target devices. This information is then transmitted from the appliance to a client which is accessing it over
the network. The time taken to execute a job depends on the available bandwidth and delay that exists in a
network.
Timeout or Non-Responsive Targets:
There are multiple cases where the communication from Power Manager to the target device may fail. There
can be a performance impact on few of the Power Manager features; especially if this happens for many
devices which are part of the task, for example, Metric Collection, Policy and EPR configurations. Possible
scenarios include discovery with incorrect credentials (or non-administrator privileges), device malfunction or
the management protocol is disabled in target devices. A WAN environment with minimum 10Mbps bandwidth
and not more than 500ms delay is recommended for seamless functionality of OpenManage Enterprise and
Power Manager tasks.
Hard Drive:
The default drive space requirements for the appliance with Power Manager 2.0 remains as mentioned in
OpenManage Enterprise version 3.6.1 User Guide. The minimum drive space requirement is 400 GB for
Small and Enterprise Deployments.