Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Sep 13, 2020

StorM performance evalution problem

StorM evaluates performance better than the actual machine.
StorM evaluates at 300,000 IOPS or more/1 msec or less under the following conditions. The bottleneck is CPU Utilization.
FS7200, 4.8TB FCM x 13, DRAID6, Read:Write=99%:1%, Block size=6KiB, iSCSI, DRP, dedupe rate=75%, compression rate=61%
I tested with FS9110 in Japan lab, but actual is 120,000 IOPS when latency is 1 msec or less.
The reason for this difference is as follows.
iSCSI processing is fixedly assigned to a specific core. When the load is increased, this core becomes the performance bottleneck.
However StorM balances CPU Utilization among the core for iSCSI and the others.This cause overestimation comparing actual machine.
StorM should be modified based on the behavior of the actual machine if a specific core becomes a bottleneck.

Idea priority Urgent