Skip to Main Content
IBM Cloud - Structured Ideas

This portal is to open public enhancement requests against IBM Cloud and its 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

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

IBM Cloud Support Center ( – Use this site for any IBM Cloud defect or support need.

Stack Overflow ( – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud". - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Feb 6, 2018

Support much bigger partition sizes

Partition sizes of 1GB on multi tenant and 10GB on dedicated are much too small for many big data and IoT use cases. Please support much bigger partitions.

The partition sizes allow you to estimate how long consumers can be offline (e.g. maintenance) before you will lose data in message hub.

If you are round robin distributing data across all partitions, you can estimate max maintenance/downstream offline time with:

    max_offline (h) =  num_partitions * max_partition_size / ingest_rate_into_mh (gb/h)


    100 partitions * 1 gb (multi tenant) / 20 gb/h = 5 hours (multi tenant) 

Based on this scenario if your downstream consumers/persistence stores are offline for more than 5 hours, you may lose data in kafka because it will be overwritten.

If you are not using round robin partitioning, and your distribution of data is not evenly spread across all of the partitions, the time to fill up a partition and overwrite data will be lower.

  • Guest
    Feb 6, 2018

    This would have assisted with a recent RFP.