Size of update packages

[i.staehli]

Hello

How can I find out the size of the update packages in Torizon Cloud?

Our devices use SIM cards to download the updates. So, knowing the size of the update packages is helpful to estimate how much an update is going to cost us.

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hello,

To find out the size of update packages in Torizon Cloud, you can follow these steps:

1. Log into Torizon Cloud: Access your Torizon Cloud account where you manage your devices and updates.

2. Navigate to the Updates Section: Look for the section related to device management or updates. This is where your update packages are typically listed.

3. View Package Details: For each update package, you should find detailed information, including the size of the package. This information is essential for estimating data usage when downloading updates via SIM cards.

4. Estimate Data Costs: With the package size information, you can calculate potential data costs based on your SIM card provider’s data rates.

By following these steps, you should be able to effectively manage and estimate the data costs associated with updating your devices using Torizon Cloud.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Offline updates usb fail

Hello, I am using verdin imx8m-plus SoM on Yavia board and I am trying to test offline updates. The torizon os version is 6.5.0 (release) I started with the online updates, I followed the documentation and used VSCode QT app template (named it torizontest), created the first version of it and uploaded with tcb-publish-platform runner to a Torizon Cloud test account. Up to this point everything worked flawlessly. I provisioned the device and I was able to run online update, by initiating it fro…

OTA update doesn't complete from Torizon Cloud.

[jeremias.tx]

Greetings @i.staehli,

Giving an answer on update size is a bit difficult and is heavily dependent on your setup. For OS type updates we use OSTree as the primary update mechanism. OSTree for the most part only downloads the differences between the files that have changed between the version you are updating to and the version you currently have.

For example if the device has OS version 1 installed and you update to version 2, maybe only a couple of files have changed between these versions so the update probably wouldn’t be that big. On the other hand if you have OS version 1 installed, but this time try to update to version 10. It’s more likely a lot of things have changed between version 1 and 10 and now the update would be significantly bigger. Furthermore, OSTree determines what needs to be downloaded right as the update is happening, so it’s not really simple to know beforehand.

With container/docker-compose updates it’s also similarly hard to tell how big an update will be without doing it first. If you notice for a container update, you actually only upload the docker-compose.yml file to our Cloud servers. We have no information about the actual docker images that your compose file points to.

When the update occurs your container images get pulled based on the compose file you provided. In a similar fashion to OSTree, if an older version of a container image already exists on the device when trying to pull a newer version than only part of the download is needed to update the container image.

As you can see it’s very specific to your setup and system how large your updates would be. In most cases you would probably need to do the update in a controlled environment and measure/monitor the network transfer to get a rough sense of how much data was needed for your specific update.

Our devices use SIM cards to download the updates. So, knowing the size of the update packages is helpful to estimate how much an update is going to cost us.

With regards to your SIM card and network costs. Do you already have in mind a data limit of sorts regarding what you would like to stay under? Or are you still exploring this?

Best Regards,
Jeremias

[i.staehli]

At the moment our updates need less than 100 MB, so that’s what we are targeting.

[jeremias.tx]

At the moment our updates need less than 100 MB, so that’s what we are targeting.

I see, that should be achievable. As long as you keep the diffs between updates small so that any one updates does not need to download a lot of data.

One more thing to mention. For OS updates only there is a type of update called “static-delta” that is even more efficient and optimized in terms of size. The trade off being a static-delta is defined between two specific versions. More information on this can be found here: Signing and Pushing Torizon OS Packages to Torizon Cloud | Toradex Developer Center

Best Regards,
Jeremias