- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- SimpliVity 4.2.0 poor IOPS
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2023 12:59 AM - last edited on 08-09-2023 05:24 AM by support_s
08-02-2023 12:59 AM - last edited on 08-09-2023 05:24 AM by support_s
SimpliVity 4.2.0 poor IOPS
Hi All,
Does anyone have the same issue as me for OVC 4.2.0 for poor IOPS and high latency storage?
and have any resolution for resolving the problem.
thanks
See
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2023 07:08 AM - edited 08-04-2023 07:09 AM
08-04-2023 07:08 AM - edited 08-04-2023 07:09 AM
Re: SimpliVity 4.2.0 poor IOPS
Hi Bouasee
I would like to suggest and provide some general guidance on troubleshooting and resolving performance issues related to HPE SimpliVity Storage and OmniStack Virtual Controllers (OVCs).
If you are experiencing poor IOPS and high latency on HPE SimpliVity Storage with OVC 4.2.0, here are some steps you can take to identify and resolve the problem:
Check Hardware Health: Verify the health status of all hardware components, including disks, memory, and network interfaces. Ensure there are no hardware failures or degradation that might be affecting performance.
Monitor Resource Utilization: Monitor resource utilization on the OVCs and storage nodes. Check CPU, memory, and storage utilization to identify if any component is experiencing excessive load.
Review Logs and Alerts: Analyze system logs and alerts for any error messages or warning signs that might indicate potential issues. Pay attention to any events related to storage, network, or cluster health.
Validate Network Connectivity: Confirm that the network connections between OVCs and storage nodes are functioning correctly and not experiencing any packet loss or latency.
Check Disk and Data Placement: Ensure that data is correctly distributed across disks and storage nodes to avoid any hotspots that might be causing performance bottlenecks.
Firmware and Software Updates: Ensure that the firmware and software versions on your HPE SimpliVity infrastructure are up to date. Updates often include performance improvements and bug fixes.
Review Configuration Settings: Review the configuration settings for the OVCs and storage nodes. Ensure that they align with best practices and any specific requirements for your environment.
Consider Workload Patterns: Examine the nature of the workloads running on the HPE SimpliVity Storage. Certain workloads might be more demanding and require specific performance optimizations.
Consider reaching out to HPE SimpliVity Tech support for assistance. They can provide further analysis and guidance in resolving performance-related issues.
Remember that performance issues can be caused by various factors, and the resolution might involve a combination of steps. It's essential to approach the troubleshooting process methodically and gather relevant data to pinpoint the root cause of the problem.
Hope this helps.!!
Regards
Mahesh.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2023 07:15 AM
08-04-2023 07:15 AM
Re: SimpliVity 4.2.0 poor IOPS
Hi Mahesh,
thank you for your reply.
to confirm for all firmware we are using is up to date for hardware and network also 25Gbps, all cluster we use only 1 virtual machine and issue found the first day we installation.
regards,
Bouasee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2023 11:55 PM
08-06-2023 11:55 PM
Re: SimpliVity 4.2.0 poor IOPS
Hi Bouasee
If you have already ensured that all firmware and software are up to date, and you are using a 25Gbps network, but are still experiencing poor IOPS and high latency with only one virtual machine in the cluster, there might be some specific configuration or underlying issues causing the problem. Here are some additional steps you can take to troubleshoot further and identify the root cause:
- Verify the configuration of the virtual machine in question. Ensure that it has enough CPU, memory, and storage resources allocated to meet its workload demands.
- Ensure that the VM's data is located on the local SimpliVity node and not accessed over the network from another node.
- The initial backup and deduplication processes might cause increased IOPS and latency during the first few days of installation. Monitor the backup and deduplication jobs to see if they are affecting VM performance.
- Monitor the resource utilization of the SimpliVity nodes to check if there is any resource contention or over utilization.
- Conduct network tests to validate the actual performance of the 25Gbps network. Check for packet loss, latency, and other potential network issues.
If you've gone through all these steps and are still experiencing issues, it's best to contact HPE SimpliVity support. They can provide in-depth analysis and assistance, as they have access to specialized tools and expertise for troubleshooting.
Hope this helps.!!
Regards
Mahesh
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2023 12:53 AM
08-07-2023 12:53 AM
Re: SimpliVity 4.2.0 poor IOPS
Hi Mahesh,
thank you for your recommend and will reply on below.
- Verify the configuration of the virtual machine in question. Ensure that it has enough CPU, memory, and storage resources allocated to meet its workload demands. >> Sure we have only 1 vm running on this
- Ensure that the VM's data is located on the local SimpliVity node and not accessed over the network from another node. >> we test on one node still same
- The initial backup and deduplication processes might cause increased IOPS and latency during the first few days of installation. Monitor the backup and deduplication jobs to see if they are affecting VM performance. >> no backup policy
- Monitor the resource utilization of the SimpliVity nodes to check if there is any resource contention or over utilization. >> resource enough for 1 vm
- Conduct network tests to validate the actual performance of the 25Gbps network. Check for packet loss, latency, and other potential network issues. >> testing a node maybe no issue for network.
I open a ticket to HPE support, but not yes have a solution to fix this.
thanks
Bouasee