Wimlib capture slow compared to acronis backup

[suresh_sairam]

Is there any way to improve the speed of Capture of operating drive with xpress compression.
Tested 50 GB OS drive with wimlib capture and acronis backup, wimlib took around 50 Minutes, while acronis true image took 26 minutes.
Tested various compression method,but very slow compared to many backup tools.

wimlib-imagex.exe capture C:\ G:\good.wim --compress=XPRESS:20 --snapshot.

[suresh_sairam]

Please Suggest a method where wimlib will perform the capture fast comparing to other backup tool. Eagerly waiting for the response.

Lakhs of users are waiting for wimlib will perform the capture very fast.

Another one thing i notice for the slow is compression of dll,zip.... can we exclude the dll,exe,zip from compression ?

[synchronicity]

With --compress=XPRESS:20, compression shouldn't be a bottleneck at all. You might have better results with a higher compression setting, e.g. --compress=XPRESS, --compress=LZX:20, or even the default of --compress=LZX. You could also try changing the number of threads (--num-threads).

But if that doesn't help, then the bottleneck is I/O and nothing can easily be done.

I'm not familiar with "Acronis True Image" and why it might be faster. Is it doing a file-level backup, or is it block-level?

[suresh_sairam]

Thank you for reply sir. Acronis is using file level backup with VSS shadowcopy.

Tested both on the same disk with with same configuration.

1 Tested .Xpress:20 with 4 ,6,8, threads with --chunksize=4096 for operating system drive. For 50 GB data almost it is taking 40 minutes. Acronis is taking 15 minutes.

2.Chunksize increased to 32k, then capture time increased to 50 minutes.

3.Can we exclude the compressed files like dll,exe from compression so that capture time will be decreased. In windows OS drive contains C:\Windows folder where it contains thousands of exe,dll.

Another point , every one expecting is continue on error (COE), even if one file gets error in reading, wim capture will abort.Please help many users by suggesting the methods for at least continue on ERROR. If we want to capture 100 GB data, if one files gets error entire capture will be failure and its waste of time for looking backup.