# Performance is really slow with high disk usage

**URL:** https://forum.duplicati.com/t/performance-is-really-slow-with-high-disk-usage/1134
**Category:** Support
**Created:** [October 23, 2017, 3:45pm UTC](https://forum.duplicati.com/t/performance-is-really-slow-with-high-disk-usage/1134 "2017-10-23T15:45:21Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![saviodsouza](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/s/bcef8e/32.png) [@saviodsouza](https://forum.duplicati.com/u/saviodsouza)
#### Post date: [October 23, 2017, 3:45pm UTC](https://forum.duplicati.com/t/performance-is-really-slow-with-high-disk-usage/1134/1 "2017-10-23T15:45:21Z")

</div>

> [@Performance is really slow with high CPU usage!](https://forum.duplicati.com/t/performance-is-really-slow-with-high-cpu-usage/1113/3):
>
> duplicati is at least 7x slower than a raw copy.

In my experience I see something I’ll call double copy… in a least complicated setup.

Backup source D:  
Temp Dir C:%temp%  
Destination E:

First read files from D:, create dblocks in temp, move to destination

No doubt the job is done but high resources are required. In this case even with no compression and encryption high HDD I/O is needed.

---

<div class="post-metadata">

### Author: ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)
#### Post date: [October 23, 2017, 4:30pm UTC](https://forum.duplicati.com/t/performance-is-really-slow-with-high-disk-usage/1134/2 "2017-10-23T16:30:51Z")

</div>

> [@Performance is really slow with high CPU usage!](https://forum.duplicati.com/t/performance-is-really-slow-with-high-cpu-usage/1113/5):
>
> In my experience I see something I’ll call double copy

For local storage like you’re using it might work better if you use `--tempdir=` to point to somewhere on E: and then `--use-move-for-put` to move the resulting files instead of copying them.

> [@Upload speed very slow, CPU near idle both ends, any ideas?](https://forum.duplicati.com/t/upload-speed-very-slow-cpu-near-idle-both-ends-any-ideas/237/15):
>
> If you are using file-based storage, you can set the options --disable-streaming-transfer and --use-move-for-put. The first disables the internal stream handling (no upload/download progress reports) and the second uses the OS “move” instead of “copy”, and thus never reading/writing the file in Duplicati.

---

<div class="post-metadata">

### Author: ![kees-z](https://forum.duplicati.com/user_avatar/forum.duplicati.com/kees-z/32/29_2.png) [@kees-z](https://forum.duplicati.com/u/kees-z)
#### Post date: [October 23, 2017, 6:26pm UTC](https://forum.duplicati.com/t/performance-is-really-slow-with-high-disk-usage/1134/3 "2017-10-23T18:26:39Z")

</div>

> [@Performance is really slow with high CPU usage!](https://forum.duplicati.com/t/performance-is-really-slow-with-high-cpu-usage/1113/5):
>
> In my experience I see something I’ll call double copy… in a least complicated setup.
> 
> Backup source D:  
> Temp Dir C:%temp%  
> Destination E:
> 
> First read files from D:, create dblocks in temp, move to destination
> 
> No doubt the job is done but high resources are required. In this case even with no compression and encryption high HDD I/O is needed.

2 ideas from @kenkendk that may improve performance and reduce disk usage:

Multithreaded backup engine:

> [@Very slow to backup](https://forum.duplicati.com/t/very-slow-to-backup/74/16):
>
> Duplicati is currently (mostly) single threaded. I am working on a version that is multithreaded. My guess is that the CPU is too slow on one core, which is why it does not upload faster (there is not enough data). I have not heard of slow-downs due to old Mono, but you could try the “aFTP” backend, as it implements the transfers a bit different.

Processing DBLOCKS and Temp files in memory:

> [@FileNotFoundException (temp file not found during backup)](https://forum.duplicati.com/t/filenotfoundexception-temp-file-not-found-during-backup/991/7):
>
> Not sure, but I would rather fix it by keeping the file “in-memory”, as it is likely to not be much of a problem (say 50-200mb file, and memory is 4GB+ on new laptops). But it is a bit of a corner case, as the file is temporary (and thus is written at the right place) but it is also used to “communicate” internally, in that it is created and passed to another method. It would be possible to keep the file open, which would prevent a cleaner program from deleting it.

---

<div class="post-metadata">

### Author: ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)
#### Post date: [October 24, 2017, 4:33am UTC](https://forum.duplicati.com/t/performance-is-really-slow-with-high-disk-usage/1134/4 "2017-10-24T04:33:26Z")

</div>

I split this off to it’s own “disk usage” specific topic as fixes for this and CPU usage issues aren’t likely to overlap much.
