title: Why not always configure for max number of event hub partitions?
body: <p>The <a href="https://azure.microsoft.com/en-us/documentation/articles/event-hubs-overview/" rel="noreferrer">Azure Event Hubs overview</a> article states the following:</p>
  
  <blockquote>
    <p>The number of partitions is specified at the Event Hub creation time
    and must be between 8 and 32. Partitions are a data organization
    mechanism and are more related to the degree of downstream parallelism
    required in consuming applications than to Event Hubs throughput. This
    makes the choice of the number of partitions in an Event Hub directly
    related to the number of concurrent readers you expect to have. After
    Event Hub creation, the partition count is not changeable; you should
    consider this number in terms of long-term expected scale. You can
    increase the 32 partition limit by contacting the Azure Service Bus
    team.</p>
  </blockquote>
  
  <p>Since you cannot change the number of partitions on your event hub after initial creation, why not just always configure it to the maximum number of partitions, 32? I do not see any <a href="http://azure.microsoft.com/en-us/pricing/details/event-hubs/" rel="noreferrer">pricing</a> implications in doing this. Is there some performance trade off?</p>
  
  <p>Also, as another side note, I appear to be able to create an event hub with less than 8 partitions. The article says it must be between 8-32. Not sure why it says that...</p>