SSD: Determine how many bytes and where it was written
You want to buy an SSD drive, but have heard a lot of scary stories about their lifespan and are afraid that you can quickly finish off your new SSD? Or are you already the owner of this disk and want to identify which applications consume the most disk resource? The utility from Sysinternals Process Monitor will help us with this. It will show how many bytes and in which files were written, as well as help to know what process it gets up. Immediately forgive me for too detailed description of the steps, I try to ensure that no one has any questions. Let's start. Download Process Monitor (no installation required) and ...
At startup, the program will ask you to create a filter (if not, then in the main menu Filter \ Filter). We need only events about accessing the disk (s) SSD (default C: \), so the filter is like this:
Path -> Begins with -> C: \ -> Include.
You add it with the Add button, then I recommend going over the filters that are lower in the list by default and removing the filters for accessing the paging file, because we need an objective opinion whether the paging file is worth keeping it on the system disk. In general, most likely it makes sense to remove almost all the filters from there, except perhaps the exclusion of Process Explorer itself from the event list.
The screenshot shows that I added the path E: \, it is only because my SSD is divided into two sections. If you have the same, do not forget to add a second path.
Next, note the time. For example, I spotted 5 minutes, and at that time I continued to do my usual activities. It may be worth checking in half an hour, although I’m not sure that the program will be able to cache so many records, although I haven’t checked it. Over time, stop logging (CTRL + E)
Go to Tools \ File summary
We are interested in the Write Bytes and Path columns. At the top, the total number of bytes written will be written, ordered by the Write Bytes column, and in the Path path we look into which files the most ardent record of bytes is kept. Not surprisingly, if it turns out to be a paging file, although if at the same time you didn’t download or close the program, it is possible that the size of the records in the paging file will not be so severe. So for example, I discovered that Opera is actively writing to the global_history.dat file, so I moved it out of harm's way. Also, the tabs on top of this window allow you to select the display mode - by files, folders and extensions. Analyze and then think for yourself what you are ready to give up for the health of SSD. Good luck!
')
ps: I accept suggestions about where this topic should be moved
0) Put the filters
At startup, the program will ask you to create a filter (if not, then in the main menu Filter \ Filter). We need only events about accessing the disk (s) SSD (default C: \), so the filter is like this:
Path -> Begins with -> C: \ -> Include.
You add it with the Add button, then I recommend going over the filters that are lower in the list by default and removing the filters for accessing the paging file, because we need an objective opinion whether the paging file is worth keeping it on the system disk. In general, most likely it makes sense to remove almost all the filters from there, except perhaps the exclusion of Process Explorer itself from the event list.
The screenshot shows that I added the path E: \, it is only because my SSD is divided into two sections. If you have the same, do not forget to add a second path.
1) The process has started
Next, note the time. For example, I spotted 5 minutes, and at that time I continued to do my usual activities. It may be worth checking in half an hour, although I’m not sure that the program will be able to cache so many records, although I haven’t checked it. Over time, stop logging (CTRL + E)
2) We look at the statistics
Go to Tools \ File summary
We are interested in the Write Bytes and Path columns. At the top, the total number of bytes written will be written, ordered by the Write Bytes column, and in the Path path we look into which files the most ardent record of bytes is kept. Not surprisingly, if it turns out to be a paging file, although if at the same time you didn’t download or close the program, it is possible that the size of the records in the paging file will not be so severe. So for example, I discovered that Opera is actively writing to the global_history.dat file, so I moved it out of harm's way. Also, the tabs on top of this window allow you to select the display mode - by files, folders and extensions. Analyze and then think for yourself what you are ready to give up for the health of SSD. Good luck!
')
ps: I accept suggestions about where this topic should be moved
Source: https://habr.com/ru/post/109654/
All Articles