Standalone Mender 1.7 taking a lot of time for deploying the artifact

I’m using the standalone mender as mentioned in the thread - here
I’m getting the below prints:

$ mender -rootfs
INFO[0000] Configuration file does not exist: /var/lib/mender/mender.conf module=config
INFO[0000] Loaded configuration file: /etc/mender/mender.conf module=config
INFO[0000] Mender running on partition: /dev/mmcblk0p2 module=main
INFO[0000] Performing remote update from: []. module=rootfs
Installing update from the artifact of size 97200128
INFO[0002] no public key was provided for authenticating the artifact module=installer
INFO[0002] opening device /dev/mmcblk0p3 for writing module=block_device
INFO[0002] partition /dev/mmcblk0p3 size: 1572864000 module=block_device
… 1% 1024 KiB
… 2% 2048 KiB
… 3% 3072 KiB
… 4% 4096 KiB
… 5% 5120 KiB
… 6% 6144 KiB
… 7% 7168 KiB
… 8% 8192 KiB
… 9% 9216 KiB

When comparing to the Mender server, It is taking a lot of time for completing the deployment. Since, the mender client is same in both the cases, why the standalone taking a lot of time when mender server done it in minutes?

Hard to comment without more specifics,

“The Mender server” is a self-hosted server? Is it hosted at the same location as the URL that you are trying to use in standalone mode.

What kind of speed to you get using “wget” and the same URL that your are providing to mender in standalone mode?

What is the time difference?

1 Like

Sorry for the confusion. It is not the problem with the mender client but, the URL server and speed.
Earlier I used Mender demo server and the speed was good. Now, I put it in a remote HTTPS server and the speed is very low.
In “wget” also I’m observing the same.