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 Mar 29, 2016

dsmc - more producer threads per filesystem

Modern SAN storage should not be limited to one producer thread per client filesystem during backups, nor 4 producer threads per DSMC instance.

Requesting:
A) RESOURCEUTIL max value should be higher, perhaps 20.

B) New option, RESTHREADSPERFS, to support multiple producer threads per filesystem, default 1 (current), and max perhaps 4 or 5.

Assumption is that the directory list would be separate from the file list, so the producer threads could always grab another directory to scan. Perhaps new directories get pushed onto the filesystem list, or whatnot.

This would not help single directory with huge numbers of files, but would help single huge filesystems with multiple directories.

Idea priority Medium
  • Guest
    Reply
    |
    Sep 10, 2018

    This seems to be partially delivered:
    * RESOURCEUTIL can be 100 as of 8.1.2
    * Still only one producer thread per filesystem.

    Recommended change: Option to cause producer threads to add directories to the queue to be scanned, rather than immediately traversing them. This would allow additional producer to process the same filesystem, one producer per directory. This would still bog down when there are a large number of small directories, or a small number of large directories. This would greatly improve backup performance of filesystems with large numbers of files fairly evenly balanced among subdirectories.