# Backup to JottaCloud extremely slow **URL:** https://forum.duplicati.com/t/backup-to-jottacloud-extremely-slow/1499 **Category:** Support **Tags:** hosting-services **Created:** [November 22, 2017, 3:57pm UTC](https://forum.duplicati.com/t/backup-to-jottacloud-extremely-slow/1499 "2017-11-22T15:57:20Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV) #### Post date: [November 22, 2017, 4:12pm UTC](https://forum.duplicati.com/t/backup-to-jottacloud-extremely-slow/1499/2 "2017-11-22T16:12:14Z")
Most often the speed complaints people have with Duplicati are due to the overhead of hashing, encrypting, and compressing the files rather than actual network bandwidth availability. Once the initial backup is completed runs tend to get quite a bit faster (depending on the amount of file changes you have in each run). * * * If you want to try and speed things up you can do things like lower the compression level (0 means no compression) or try a different hashing algorithm as discussed here: > [@Performance is really slow with high CPU usage!](https://forum.duplicati.com/t/performance-is-really-slow-with-high-cpu-usage/1113/2): > > There currently isn’t a “here are the slow parts” profiling function, but the Live Log does have a profiling mode that shows pretty much everything being done and how long it takes, but it’s not pretty. Some discussion has happened around adding metrics, but so far development time has been focused on functionality. Are you getting these 1GB/min times on initial backups, subsequent runs, or both? As far as what Duplicati is doing, the summary is (sort of in this order): compare list of curr… * * * Also, you didn’t mention what Duplicati version you’re running but the later Canary versions include improved hashing as mentioned here: > [@Performance is really slow with high CPU usage!](https://forum.duplicati.com/t/performance-is-really-slow-with-high-cpu-usage/1113/16): > > Apart from the parallel hashing, there is another speedup in the canary that uses the (terribly named) NgHash. But you can also get it to use the OpenSSL hashing library, which is faster in my tests. You need to drop in the version of the OpenSSL library you are using from here: [FasterHashing/Windows-DLLs at master · kenkendk/FasterHashing · GitHub](https://github.com/kenkendk/FasterHashing/tree/master/Windows-DLLs) Then set the environment variable FH\_LIBRARY=openssl and it should load OpenSSL and use that for hashing. * * * This post has a slightly more detailed list of what Duplicati is doing during the backups: > [@Performance is really slow with high CPU usage!](https://forum.duplicati.com/t/performance-is-really-slow-with-high-cpu-usage/1113/2): > > There currently isn’t a “here are the slow parts” profiling function, but the Live Log does have a profiling mode that shows pretty much everything being done and how long it takes, but it’s not pretty. Some discussion has happened around adding metrics, but so far development time has been focused on functionality. Are you getting these 1GB/min times on initial backups, subsequent runs, or both? As far as what Duplicati is doing, the summary is (sort of in this order): compare list of curr… --- _[View the full topic](https://forum.duplicati.com/t/backup-to-jottacloud-extremely-slow/1499)._