IBM System Storage Ideas Portal
Hide about this 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.

Add a new idea Subscribe
Status Delivered
Workspace Storage Protect Family
Categories Spectrum Protect (Server)
Created by Guest
Created on Sep 25, 2017

RELATED IDEAS

Improve Logical Block Protection performance by using faster CRC implementation

See this idea on ideas.ibm.com

The Logical Block Protection (LBP) feature in Spectrum Protect (TSM) is currently limiting performance when used with current generation tape drives. In production we see around 360 MB/s without LBP enabled, degrading to around 200 MB/s with LBP enabled. Investigation using the perf top utility shows that a large contribution to this performance degradation seems to be the CRC implementation used in the TSM server. Further comparison using the crcspeed benchmark [1] supports this conclusion, as the commonly used lookup table CRC implementation performs at around 300 MB/s while a modern fast implementation yields more than 1500 MB/s on our production system.

We propose that CRC performance in the TSM server is enhanced by using a modern fast CRC implementation, for example slicing-by-N. The crcspeed benchmark, which uses slicing-by-8, shows that dramatic speedup is possible for CRC16 (which is the CRC used by LBP tape drives), eliminating the CRC process itself as a bottleneck for the immediate future. Furthermore, [2] suggests that slicing-by-16 shows even better performance for CRC32, and thus might have similar properties for other CRC sizes.

[1] https://github.com/mattsta/crcspeed

[2] http://create.stephan-brumme.com/crc32/

Idea priority High
  • Guest
    Reply
    |     Sep 20, 2018

    This item is include in Spectrum Protect 8.1.6 (target is 21 September 2018).

  • Guest
    Reply
    |     Sep 10, 2018

    This RFE has the highest vote count of any SP/TSM RFE I've run across. Please consider upgrading this from "Uncommitted Candidate" to "Planned for Future Release".

    We see this as a huge CPU hit on our secondary/cloud servers. We have enough CPU for now, but find that our cloud servers use 4-5x the CPU vs our front-end ingest servers for the same amount of data movement.

  • Guest
    Reply
    |     Jun 29, 2018

    This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.