Раздачи :: Другое - Программы :: O&O Defrag 22 (Professional Edition, v. 22.0) / x86 + x64 / RU / Система / 2018 / RePack+Portable (TryRooM) / PC (Windows) :: Комментарии
- Меню раздачи
- Другие версии
- Добавить в закладки
- Позвать скачавших
- Участники
- Раздают0
- Скачивают0
- Скачали274
- Список файлов5
- Комментариев8
- Залил раздачу
avgur79- Голосование
- Оценка10.0 из 10
- Голосов8
- Просим Вас оценивать материал после ознакомления с ним. Ваши оценки вы можете просмотреть здесь
- Опубликовать ссылку
- Характеристика
- Вес16 МБ (16,690,884)
- Залит19 декабря 2013 в 12:14
- Обновлен23 сентября 2018 в 18:14
 | Для того, чтобы скачать раздачу - скачайте торрент-файл и запустите его при помощи клиента. Дополнительная информация на Форуме здесь. |
( Закрыть )
loading...
Комментарии ( Комментировать )
Что нового:
Our new O&O Defrag 22 Pro is now available with some groundbreaking new features!
Windows – and in the case of SSDs, the controller of the SSD – distributes files into individual file fragments when saved, in each case in the next free and “suitable” memory sections, called Pages. In the remainder of this blog entry, I explain why this behavior slows down not only a classic hard drive but also SSDs and ultimately leads to an unnecessarily early failure of the storage medium. And I’ll explain why defragmenting an SSD is not a no-go, as is still popularly claimed, but on the contrary: the average life of an SSD is extended by defragmentation using the new SOLID method from O&O Defrag 22.
How is an SSD structured?
An SSD consists of cells, pages and blocks. A cell can be several bits in size. The manufacturer marks this cell with either SLC, MLC or TLC. The SLC are the SingleLevelCells (1 bit per cell), the MLC the MultiLevelCells (from 2 bits per cell, but mostly exactly 2 bits and TLC are the TripleLevelCells (3 bits per cell). Pages are made up of cells and typically have a size of 2KB – 4KB. The Blocks then consist of these pages, and usually have a size of 128KB – 512KB.
How does an SSD store data?
Writing data to an SSD is essentially done in Pages. However, these pages should not already be written with data (not even if they have the same content). If these pages are written with data, the corresponding block must be deleted immediately before any new data can be written. When writing new data however, no block can be selected whose other pages also already contain data. The SSD Controller can see that the other pages contain data, but cannot see to which file they belong. So in a nutshell, in order not to accidentally damage an important file by deleting data from it on the block, you have to search for an entirely free block to save data on.
Why is fragmentation problematic with SSDs?
Files are often stored in pieces (fragments) onto the disk or onto the file system. The size of the fragments depends on the cluster size of the respective file system (normally 4KB in NTFS). Let’s assume a block on our SSD is 128KB and a file (128KB) that is split into 32 fragments needs to be saved (you recall, each fragment will be 4KB large). In the worst-case scenario, this would then have to be saved on 32 different blocks. If this file had only one “fragment”, one single block would be enough. The problem then with writing such a fragmented file: The controller has to find 32 FREE blocks and, in the worst-case, delete them all. Then it must write to these 32 blocks as well – and this must happen every time a file is changed too!
NEW: SOLID, a brand-new defrgamentation method for SSDs and HDDs
The problem: SSDs store file fragments spread across many blocks, even though much fewer would suffice.
This memory behavior has an immediate effect on the performance and lifespan of an SSD. To counteract wear and at the same time to optimize the performance of SSDs, O&O Software has developed the new defragmentation method SOLID. By using the defragmentation method SOLID, these distributed file parts are defragmented so that in the future significantly fewer memory cells have to be read out and also written to when changing a file. As a result, the SSD is faster as the number of read and write accesses is reduced by the defragmentation. In addition, the premature wear of the SSD (and of course the conventional hard drive) is prevented because fewer blocks need to be erased and rewritten than before the defragmentation with SOLID. To stay with our example above: To read our sample file, it is not necessary to first access and read 32 different blocks, but only a single one.
The most comprehensive tuning application for all your disks
A positive side-effect of developing the defragmentation method SOLID has been found in tests on “classic” hard disks: it is O&O Defrag’s most resource and hardware-friendly defragmentation method ever, with optimal results, and sets the new standard for defragmentation.
As we mention above, files are also fragmented on SSDs. Data is often distributed to more memory cells than would be necessary. By defragmenting an SSD using our new method SOLID, it is possible to reduce the number of cells used to store file parts down to significantly fewer.
Let O&O Defrag 22 Pro optimize your hard disks and SSDs, and you will get more speed while at the same time saving money on your hardware.
Our new O&O Defrag 22 Pro is now available with some groundbreaking new features!
Windows – and in the case of SSDs, the controller of the SSD – distributes files into individual file fragments when saved, in each case in the next free and “suitable” memory sections, called Pages. In the remainder of this blog entry, I explain why this behavior slows down not only a classic hard drive but also SSDs and ultimately leads to an unnecessarily early failure of the storage medium. And I’ll explain why defragmenting an SSD is not a no-go, as is still popularly claimed, but on the contrary: the average life of an SSD is extended by defragmentation using the new SOLID method from O&O Defrag 22.
How is an SSD structured?
An SSD consists of cells, pages and blocks. A cell can be several bits in size. The manufacturer marks this cell with either SLC, MLC or TLC. The SLC are the SingleLevelCells (1 bit per cell), the MLC the MultiLevelCells (from 2 bits per cell, but mostly exactly 2 bits and TLC are the TripleLevelCells (3 bits per cell). Pages are made up of cells and typically have a size of 2KB – 4KB. The Blocks then consist of these pages, and usually have a size of 128KB – 512KB.
How does an SSD store data?
Writing data to an SSD is essentially done in Pages. However, these pages should not already be written with data (not even if they have the same content). If these pages are written with data, the corresponding block must be deleted immediately before any new data can be written. When writing new data however, no block can be selected whose other pages also already contain data. The SSD Controller can see that the other pages contain data, but cannot see to which file they belong. So in a nutshell, in order not to accidentally damage an important file by deleting data from it on the block, you have to search for an entirely free block to save data on.
Why is fragmentation problematic with SSDs?
Files are often stored in pieces (fragments) onto the disk or onto the file system. The size of the fragments depends on the cluster size of the respective file system (normally 4KB in NTFS). Let’s assume a block on our SSD is 128KB and a file (128KB) that is split into 32 fragments needs to be saved (you recall, each fragment will be 4KB large). In the worst-case scenario, this would then have to be saved on 32 different blocks. If this file had only one “fragment”, one single block would be enough. The problem then with writing such a fragmented file: The controller has to find 32 FREE blocks and, in the worst-case, delete them all. Then it must write to these 32 blocks as well – and this must happen every time a file is changed too!
NEW: SOLID, a brand-new defrgamentation method for SSDs and HDDs
The problem: SSDs store file fragments spread across many blocks, even though much fewer would suffice.
This memory behavior has an immediate effect on the performance and lifespan of an SSD. To counteract wear and at the same time to optimize the performance of SSDs, O&O Software has developed the new defragmentation method SOLID. By using the defragmentation method SOLID, these distributed file parts are defragmented so that in the future significantly fewer memory cells have to be read out and also written to when changing a file. As a result, the SSD is faster as the number of read and write accesses is reduced by the defragmentation. In addition, the premature wear of the SSD (and of course the conventional hard drive) is prevented because fewer blocks need to be erased and rewritten than before the defragmentation with SOLID. To stay with our example above: To read our sample file, it is not necessary to first access and read 32 different blocks, but only a single one.
The most comprehensive tuning application for all your disks
A positive side-effect of developing the defragmentation method SOLID has been found in tests on “classic” hard disks: it is O&O Defrag’s most resource and hardware-friendly defragmentation method ever, with optimal results, and sets the new standard for defragmentation.
As we mention above, files are also fragmented on SSDs. Data is often distributed to more memory cells than would be necessary. By defragmenting an SSD using our new method SOLID, it is possible to reduce the number of cells used to store file parts down to significantly fewer.
Let O&O Defrag 22 Pro optimize your hard disks and SSDs, and you will get more speed while at the same time saving money on your hardware.
