IoT Edge Task is quite slow
See original GitHub issueType: Bug
Enter Task Name: AzureIoTEdgeV2
Environment
-
Server - Azure Pipelines
-
Agent - Hosted
- agent pool name: Azure Pipelines
Issue Description
When executing any of the action of this this takes so long. We even replaced actions build and push with docker tasks because this is much faster. Unfortunetely for Generate Deployment manifest and Deploy to IoT Edge devices we have no choice other than to use this task. Action Generate Deployment manifest takes ~1min36sec to execute. It’s just generating a json document. Action Deploy to IoT Edge devices takes ~1min27sec to execute. It’s just sending a json document to IoT Hub.
Task logs
Action Generate Deployment manifest
Starting: Azure IoT Edge - Generate deployment manifest
==============================================================================
Task : Azure IoT Edge
Description : Build and deploy an Azure IoT Edge image
Version : 2.4.4
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/azure-iot-edge
==============================================================================
Start generating deployment manifest...
/home/vsts/work/1/s/*** /home/vsts/work/1/s
iotedgedev installed with version: version 2.1.0
/usr/local/bin/iotedgedev genconfig --file /home/vsts/work/1/s/***/deployment.template.json --platform amd64 --fail-on-validation-error
=======================================
======== ENVIRONMENT VARIABLES ========
=======================================
.env file not found on disk. Without a file on disk, you must specify all Environment Variables at the system level. (/home/vsts/work/1/s/***/.env)
Welcome to iotedgedev!
-------------------------
Telemetry
---------
The iotedgedev collects usage data in order to improve your experience.
The data is anonymous and does not include commandline argument values.
The data is collected by Microsoft.
You can change your telemetry settings by updating 'collect_telemetry' to 'no' in /home/vsts/.iotedgedev/setting.ini
Validating deployment template /home/vsts/work/1/s/***/deployment.template.json
Validating schema of deployment template.
Deployment template schema validation passed.
Expanding image placeholders
Converting createOptions
Deleting template schema version
Expanding 'deployment.template.json' to '/home/vsts/work/1/s/config/deployment.json'
Validating generated deployment manifest /home/vsts/work/1/s/config/deployment.json
Validating schema of deployment manifest.
Deployment manifest schema validation passed.
Start validating createOptions for all modules.
Validating createOptions for module azureiotsecurity
createOptions of module azureiotsecurity validation passed
Validating createOptions for module SILverPreprocessing
createOptions of module SILverPreprocessing validation passed
Validating createOptions for module Preprocessing
createOptions of module Preprocessing validation passed
Validating createOptions for module InfluxDb
createOptions of module InfluxDb validation passed
Validating createOptions for module Grafana
createOptions of module Grafana validation passed
Validating createOptions for module edgeAgent
createOptions of module edgeAgent validation passed
Validating createOptions for module edgeHub
createOptions of module edgeHub validation passed
Validation for all createOptions passed.
Finished generating deployment manifest.
Finishing: Azure IoT Edge - Generate deployment manifest
Action Deploy to IoT Edge devices
Starting: Azure IoT Edge - Deploy to IoT Edge devices
==============================================================================
Task : Azure IoT Edge
Description : Build and deploy an Azure IoT Edge image
Version : 2.4.4
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/azure-iot-edge
==============================================================================
Start deploying...
Deployment task is running in build pipeline? true
/home/vsts/work/1/s/config/deployment.json
Checking if the following file is a valid json: /home/vsts/work/1/s/config/deployment.json
Valid
Normalized deployment id is: ***
/usr/bin/az iot edge deployment create --deployment-id *** --hub-name *** --content /tmp/deployment_1606380786373.json --target-condition *** --priority 100 --output none
Finished Deploying
Finishing: Azure IoT Edge - Deploy to IoT Edge devices
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Troubleshoot your IoT Edge device - Azure - Microsoft Learn
If you experience issues running Azure IoT Edge in your environment, use this article as a guide for troubleshooting and diagnostics.
Read more >Slow response sending data to IoT Hub using Device Client
I have about 3k-4k requests every minute and the above code gets called for each request. It has really started being unreliable since...
Read more >Exam AI-100 topic 4 question 31 discussion - ExamTopics
You have Azure IoT Edge devices that generate measurement data from temperature sensors. The data changes very slowly.
Read more >The problem that I am having is that IoT updates t... - PTC Community
That said, it controls the pump from the cloud in real time I think, but the flow sensor update is too slow to...
Read more >IoT Show: Azure IoT Edge monitoring and troubleshooting
In this episode, Venkat Yalla, Principal Program Manager in the Azure IoT Ege tells us about the new, first-class IoT Edge remote monitoring ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@oliverchristen thank you for reporting this issue. We have added it to our backlog for investigations and will follow up with any findings on this thread.
Hi @cindydeng1998 We have the same problem with slow execution, we have many deployments, if there are dependancies would it be possible to generate/deploy multiple manifests in a single command thereby only loading the dependancies once?