title: Azure Functions EventHub trigger scale job function instances
body: <p>I have an Azure Function that has EventHub trigger, with Consumption plan. In my test I shoot 3000 events to event hub using in a few batches. Since time for those 3000 events was almost 10 times bigger than the time for 300 events, I suspected that this Azure Function didn't scale to multiple VMs/instances.</p>
  
  <p>To verify that hypothesis, I used a Guid static variable, which I initialized once and logged in every run of the function. All 3000 runs logged the same Guid.</p>
  
  <p>That happens even if I specify following configuration in host.json:
  "eventHub": {
        "maxBatchSize": 1,
        "prefetchCount": 10
      }</p>
  
  <p>Logic was that this would limit parallel processing within single instance and multiple instances would be started because of that, but again only 1 Guid is logged.</p>
  
  <p>As a note, this is not the only function in App Service. Could that be the issue? What is the condition that needs to be satisfied so that Function is started on multiple VMs?</p>
  
  <p><strong>Edit</strong>:
  I have 32 partitions and 20 throughput units. First issue was that I was using SendBatchAsync, which doesn't partition events. Even SendAsync didn't bring any scale, like it wasn't partitioning. So I created partitioned eventhub senders and did round robin partitioning when sending events in client application.</p>
  
  <p>That increased number of events processed by AzureFunction, but still didn't create more than 1 VM.
  Furthermore, number of events processed per second was much larger in the beginning (~200 in each moment), and after 2000 events, or near the end, they dropped to ~5. This has nothing to do with load of the system, as same behavior was observed with 9000 events, where slowing down happened after ~5k events.</p>
  
  <p>This Azure function lasts 50-250 ms, depending on the load.
  It also sends event to another Azure function through Azure Storage Queue trigger. What is interesting is that neither that function which is triggered by Queue trigger scales to more than 1 VM, and it has ~1k messages in queue at the beginning, before slowness of eventhub triggered azure function. Queue settings in host.json are "queues": {
        "maxPollingInterval": 2000,
        "visibilityTimeout" : "00:00:10",
        "batchSize": 32,
        "maxDequeueCount": 5,
        "newBatchThreshold": 1
      }</p>
  
  <p>Thanks.</p>