This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 73
How to increase the throughput of the Simulation Service
Devis Lucato edited this page Jun 23, 2018
·
4 revisions
Following are instructions on how to change the message per second limit for the service. These should be used with care as following this guide could lead to the IoT Hub throttling the service. To prevent throttling you should add more Units to your IoT Hub or change the SKU; e.g. from an S2 level to an S3 level to match the parameters you set.
Please read the following guide for background on IoT Hub throttling: https://docs.microsoft.com/azure/iot-hub/iot-hub-devguide-quotas-throttling
- Resize IoT Hub:
- Open the Azure portal, go to the Resource Group containing the resources created
- Change IoT Hub SKU from S2 to S3
- You might also want to increase the VM size, from 4 cores to 8 cores or more (you can do this later if you don’t reach the desired throughput)
- Customize configuration:
- SSH into the VM
- Create a custom configuration file
sudo nano /app/device-simulation-appsettings.ini
- Copy the content of appsettings.ini into this file
- Change lines 67-97 with IoT Hub S3 quota limits (see comments)
- Save (CTRL+X)
- Edit Docker Compose file:
sudo nano /app/docker-compose.yml
- Uncomment lines 56-57, so that Docker Compose will use the custom configuration file
- Save (CTRL+X)
- Restart the microservices:
sudo /app/start.sh