A while ago - in July 2017 - I compared the performance of wimlib and DISM when creating a new backup.
DISM ran for 10 minutes and produced a WIM file of 13 GB
WimLib ran for 56 minutes and produced a WIM file of 12 GB
I performed these tests one after the other for the same partition on the ...
Search found 5 matches
- Sat Jan 20, 2018 4:43 pm
- Forum: wimlib discussion
- Topic: Performance of wimlib vs. DISM
- Replies: 1
- Views: 12041
- Sun May 14, 2017 8:48 pm
- Forum: wimlib discussion
- Topic: WimLibScripts using WimLib
- Replies: 2
- Views: 13286
Re: WimLibScripts using WimLib
Thanks for your comments.
I removed the --solid flag to make the images more DISM compatible.
Version v1.10.0 exhibited the sparse file issue. I'll test version v1.11.0 and update the manual accordingly.
I examined all available properties of the WIM images.
I'll have a closer look at if and how I ...
I removed the --solid flag to make the images more DISM compatible.
Version v1.10.0 exhibited the sparse file issue. I'll test version v1.11.0 and update the manual accordingly.
I examined all available properties of the WIM images.
I'll have a closer look at if and how I ...
- Sat Mar 25, 2017 11:42 am
- Forum: wimlib discussion
- Topic: WimLibScripts using WimLib
- Replies: 2
- Views: 13286
WimLibScripts using WimLib
Check out http://github.com/FrankHeimes/WimLibScripts
I crafted a few scripts for backup and restore using the WimLib library.
Comments highly appreciated.
I crafted a few scripts for backup and restore using the WimLib library.
Comments highly appreciated.
- Mon Mar 13, 2017 11:45 pm
- Forum: wimlib discussion
- Topic: Extracted image occupies more space than original
- Replies: 1
- Views: 10291
Extracted image occupies more space than original
I created a backup from a Windows 10 volume, that was offline.
Then I restored the image to another, empty volume.
The restored Image on the second volume consumes about 3% more space than the original volume.
To double check, I created another backup of the extracted volume.
Comparing the file ...
Then I restored the image to another, empty volume.
The restored Image on the second volume consumes about 3% more space than the original volume.
To double check, I created another backup of the extracted volume.
Comparing the file ...
- Mon Mar 13, 2017 11:12 pm
- Forum: wimlib discussion
- Topic: Total Bytes of an image appears too large
- Replies: 1
- Views: 10122
Total Bytes of an image appears too large
I had just created a backup of a volume with 16 GB of data.
This resulted in a WIM Image of about 6 GB in size.
The info command returns the following summary about that Image ( I removed some lines ):
WIM Information:
----------------
Image Count: 1
Compression: LZMS
Chunk Size: 131072 bytes
Size ...
This resulted in a WIM Image of about 6 GB in size.
The info command returns the following summary about that Image ( I removed some lines ):
WIM Information:
----------------
Image Count: 1
Compression: LZMS
Chunk Size: 131072 bytes
Size ...