1 |
Am Wed, 20 Jan 2016 01:46:29 +0100 |
2 |
schrieb lee <lee@××××××××.de>: |
3 |
|
4 |
> The time before, it wasn't |
5 |
> a VM but a very slow machine, and that also took a week. You can have |
6 |
> the fastest machine on the world and Windoze always manages to bring |
7 |
> it down to a slowness we wouldn't have accepted even 20 years ago. |
8 |
|
9 |
This is mainly an artifact of Windows updates destroying locality of |
10 |
data pretty fast and mainly a problem when running on spinning rust. |
11 |
DLLs and data files needed for booting or starting specific |
12 |
software become spread wide across the hard disk. Fragmentation isn't |
13 |
the issue here - NTFS is pretty good at keeping it low. Still, the |
14 |
right defragmentation tool will help you: I always recommend staying |
15 |
away from the 1000 types of "tuning tools", they actually make it worse |
16 |
and take away your chance of properly optimizing the on-disk file |
17 |
layout. And I always recommend using MyDefrag and using its system disk |
18 |
defrag profile to reorder the files in your hard disk. It takes ages |
19 |
the first time it runs but it brings back your system to almost out of |
20 |
the box boot and software startup time performance. It uses some very |
21 |
clever ideas to place files into groups and into proper order - other |
22 |
than using file mod and access times like other defrag tools do (which |
23 |
even make the problem worse by doing so because this destroys locality |
24 |
of data even more). |
25 |
|
26 |
But even SSDs can use _proper_ defragmentation from time to time for |
27 |
increased lifetime and performance (this is due to how the FTL works |
28 |
and because erase blocks are huge, I won't get into detail unless |
29 |
someone asks). This is why mydefrag also supports flash optimization. |
30 |
It works by moving as few files as possible while coalescing free space |
31 |
into big chunks which in turn relaxes pressure on the FTL and allows to |
32 |
have more free and continuous erase blocks which reduces early flash |
33 |
chip wear. A filled SSD with long usage history can certainly gain back |
34 |
some performance from this. |
35 |
|
36 |
-- |
37 |
Regards, |
38 |
Kai |
39 |
|
40 |
Replies to list-only preferred. |