It was possibly time a tuneup of the SSD on my laptop, so I fired up the Windows To Go with VM. Checked the performance with RS and HD Tune Free.
RS: 193.2 1388.4 302.8 299.0 341.5
The benchmarks suggested an L3 on the full disk might be beneficial. SR worked fine but it took a bit longer than the initial estimate suggested. There were some interesting results. The huge spikes in the TD Tune graph pre SR were likely due to unused sectors. The L3 activity would have marked them as active as shown in the relatively flat graph below.
Two measurements were taken for RS and SR Benchmark after the L3 run. The results were quite different.
A. Results using the drive configured using an IDE controller:
RS: 203.4 321.9 317.0 323.7 320.9
SR: 239.178 322.109 326.079
B. Results using the drive configured using an AHCI controller:
RS: 516.7 1327.1 1346.4 1314.9 1298.9
SR: 188.438 261.793 263.023
Analysis:
1. SR & RS using the IDE controller give relatively similar results, but slower results over the first section.
2. RS is significantly faster using AHCI (assume this is due the the different built-in drivers in these two apps)
3. SR is slower using the AHCI controller than the IDE controller (also due to built-in drivers)
Conclusions:
1. TD Tune seems to be a reasonable tool to determine if/when/where an L3 should be performed.
2. Readspeed using an AHCI controller provides unrealistic results
3. The relatively slow results, by both SR and RS, over the first part of the drive is inconsistent with HD Tune. L3 should have improved this area. Not sure why this does not show in the results with RS and SR, but does with TD Tune..
RS: 193.2 1388.4 302.8 299.0 341.5
The benchmarks suggested an L3 on the full disk might be beneficial. SR worked fine but it took a bit longer than the initial estimate suggested. There were some interesting results. The huge spikes in the TD Tune graph pre SR were likely due to unused sectors. The L3 activity would have marked them as active as shown in the relatively flat graph below.
Two measurements were taken for RS and SR Benchmark after the L3 run. The results were quite different.
A. Results using the drive configured using an IDE controller:
RS: 203.4 321.9 317.0 323.7 320.9
SR: 239.178 322.109 326.079
B. Results using the drive configured using an AHCI controller:
RS: 516.7 1327.1 1346.4 1314.9 1298.9
SR: 188.438 261.793 263.023
Analysis:
1. SR & RS using the IDE controller give relatively similar results, but slower results over the first section.
2. RS is significantly faster using AHCI (assume this is due the the different built-in drivers in these two apps)
3. SR is slower using the AHCI controller than the IDE controller (also due to built-in drivers)
Conclusions:
1. TD Tune seems to be a reasonable tool to determine if/when/where an L3 should be performed.
2. Readspeed using an AHCI controller provides unrealistic results
3. The relatively slow results, by both SR and RS, over the first part of the drive is inconsistent with HD Tune. L3 should have improved this area. Not sure why this does not show in the results with RS and SR, but does with TD Tune..
