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 Feb 6, 2013

Optimize Write IO behaviour on DISK

Using diskpools (deviceclass=disk) or filepools (deviceclass=file) on a non-cached disk system is very slow, and therefore not usable.
Example (same setup in both cases):
TSM write to diskpoolon 8x Internal DISK = 8MB/s
AIX cp command on 8x Internal DISK = 300MB/s

The difference (as I understand it) is that the AIX cp command uses JFS2 read ahead and write behind mechanisms. TSM on the other hand waits for each 256KB write to complete before writing another 256KB block.
What we would like to see is that TSM would allow more 256KB blocks to be "in flight" (maybe using a parameter like "queuedepth" so it can be tuned) so that even on a non-cached disk system or wenn higher latencies occur on a cached disksystem, the disk can perform sequential IO and write multiple blocks at once and so improving throughput.

Idea priority High
  • Guest
    Reply
    |
    Jun 12, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

  • Guest
    Reply
    |
    Apr 4, 2014

    Thank you for submitting this request. In the case of disk with no write cache performance may be improved by turning off direct I/O via setting DIRECTIO NO in dsmserv.opt. This will allow the operating system to cache more data, resulting in better performance in that case. More information about this option is available in the TSM documentation: http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1/index.jsp?topic=%2Fcom.ibm.itsm.perf.doc%2Ft_ptg_filesys_cache.html&resultof%3D%2522%2564%2569%2572%2565%2563%2574%2569%256f%2522%2520.