Reflect X vs Hasleo v4.9.3
CPU: i7-10700, 8-core/16-thread, 2.9/4.8ghz
RAM: 32gB
Source disk: NvME M2.2280, PCiE v3 (7-part <1 [email protected], 1 unf@16mB, 1 [email protected], 1 [email protected],
-------------------------------------------------------- 1 [email protected], 1 [email protected] & 1 [email protected])
Target disk: NvME M2.2280, PCiE v3
MEDIUM compression, no image checks following imaging operation
Hasleo v4.9.3: 4m 57s (Image size=83.5gB)
Reflect v10: 3m 9s (Image size=71.4)
Remember, Macrium REFLECT X is now using an entirely new streaming compression method, when imaging, obtained from a Facebook developer. As a result, the image format (not the method) is now PUBLIC and available to all if interested.
I'm not sure if Hasleo is able to determine the USED SECTOR amount with EXT<n> images... that may be the main reason for the differences in image sizes. I'm sure the ADMIN (Dev Team rep) will jump in here and correct this assumption, if necessary.
CPU: i7-10700, 8-core/16-thread, 2.9/4.8ghz
RAM: 32gB
Source disk: NvME M2.2280, PCiE v3 (7-part <1 [email protected], 1 unf@16mB, 1 [email protected], 1 [email protected],
-------------------------------------------------------- 1 [email protected], 1 [email protected] & 1 [email protected])
Target disk: NvME M2.2280, PCiE v3
MEDIUM compression, no image checks following imaging operation
Hasleo v4.9.3: 4m 57s (Image size=83.5gB)
Reflect v10: 3m 9s (Image size=71.4)
Remember, Macrium REFLECT X is now using an entirely new streaming compression method, when imaging, obtained from a Facebook developer. As a result, the image format (not the method) is now PUBLIC and available to all if interested.
I'm not sure if Hasleo is able to determine the USED SECTOR amount with EXT<n> images... that may be the main reason for the differences in image sizes. I'm sure the ADMIN (Dev Team rep) will jump in here and correct this assumption, if necessary.