Hasleo Backup Suite V5.5.2.1 Released!

[admin]

I have some more info that may help to explain why I am seeing a difference between the backup times using V5.4.2.5 and V5.5.2.1
The 2 PCs I have run the tests on previously are a 12thGen Intel i5 desktop and a 13thGen Intel i7 laptop.
Both of these CPUs have a mix of Performance and Efficiency cores. Its up to the thread director to allocate which cores perform which tasks.

I thought I would try the same tests on an older laptop with a  8thGen i7. This just has 4 regular cores with hyperthreading.

V5425:
Backing up to an internal SSD took 2m40s
Backing up an ext USB HDD took 6m14s

V5521:
Backing up to an internal SSD took 2m43s
Backing up an ext USB HDD took 6m14s

The external USB HDD was the same 2TB Toshiba device i have used in all my previous tests.
As you can see above, the backup times are now virtually identical between the 2 versions of Hasleo.

So, could my previous results be down to the way the cores are being allocated on 12th and 13th gen Intel CPUs?

I vaguely recall that you mentioned in another forum thread that you were developing  using AMD based PCs which don't currently feature the mix of Performance and Efficiency cores like recent Intel devices do.

Anyway, food for thought.

In fact, we conducted tests on computers with both Intel and AMD CPUs. As you know, SATA HDD speeds are typically slow (around 200 MB/s). Therefore, it does not require a powerful CPU to process data to reach the maximum write speed of an HDD. Furthermore, since you mentioned that the issue does not occur when the target drive is an SSD, the problem is unlikely to be caused by CPU performance.

Our recommendation is to please perform the backup again, ensuring that the source and target drives are exactly the same. While doing so, monitor the CPU and disk I/O usage, as this may reveal useful clues.

Thanks.