F5F Stay Refreshed Hardware Desktop Performing 10TB of SSD operations over 84 hours of continuous use.

Performing 10TB of SSD operations over 84 hours of continuous use.

Performing 10TB of SSD operations over 84 hours of continuous use.

Pages (3): Previous 1 2 3
Q
Quirky_Q
Junior Member
25
07-31-2016, 11:49 AM
#21
No, I haven't used any anti-malware or antivirus tools yet.
Q
Quirky_Q
07-31-2016, 11:49 AM #21

No, I haven't used any anti-malware or antivirus tools yet.

B
bishopboys68
Posting Freak
899
07-31-2016, 12:03 PM
#22
It seems the crystal disk mark might have misinterpreted the information. This software processes raw drive data and could produce errors. I’d try using the Lexar SSD utility to check the reported write data.
B
bishopboys68
07-31-2016, 12:03 PM #22

It seems the crystal disk mark might have misinterpreted the information. This software processes raw drive data and could produce errors. I’d try using the Lexar SSD utility to check the reported write data.

B
Bhdrglr7
Member
55
08-04-2016, 12:26 AM
#23
Below are the results from both Lexar and DiskInfo tools. Frequently, data flows between System or Registry at about 20–40 MB per second. Over a minute that equals 1.2GB to 2.4GB. DiskInfo shows roughly 1 GB added each minute, but SSD capacity stays steady around 142 GB used. It seems the system writes and then clears information. You might investigate further tomorrow with an antivirus scan.
B
Bhdrglr7
08-04-2016, 12:26 AM #23

Below are the results from both Lexar and DiskInfo tools. Frequently, data flows between System or Registry at about 20–40 MB per second. Over a minute that equals 1.2GB to 2.4GB. DiskInfo shows roughly 1 GB added each minute, but SSD capacity stays steady around 142 GB used. It seems the system writes and then clears information. You might investigate further tomorrow with an antivirus scan.

I
iLeslie
Junior Member
39
08-05-2016, 05:34 PM
#24
Lexar is focusing on sectors rather than GB, which seems more practical. It's unclear the exact size of the drive, but I think writing in any part of a sector forces the entire sector to be rewritten, including all Windows services that produce logs. EDIT: some research indicates the sector might be 32MB, leading to sensible total write estimates.
I
iLeslie
08-05-2016, 05:34 PM #24

Lexar is focusing on sectors rather than GB, which seems more practical. It's unclear the exact size of the drive, but I think writing in any part of a sector forces the entire sector to be rewritten, including all Windows services that produce logs. EDIT: some research indicates the sector might be 32MB, leading to sensible total write estimates.

K
157
08-11-2016, 07:11 PM
#25
The write sector count of 9884 * 32mb indicates roughly 316gB of data written, which appears accurate. I won’t focus on crystal disk mark; I believe those values are likely incorrect. It’s probably not capturing the numbers correctly. You might try recording a known size write, such as 10gb, to check how the total changes. Based on this, the 300gB written seems reasonable. Since the task manager doesn’t display write activity, it’s unlikely actual data is being written.
K
KariibikUrlxub
08-11-2016, 07:11 PM #25

The write sector count of 9884 * 32mb indicates roughly 316gB of data written, which appears accurate. I won’t focus on crystal disk mark; I believe those values are likely incorrect. It’s probably not capturing the numbers correctly. You might try recording a known size write, such as 10gb, to check how the total changes. Based on this, the 300gB written seems reasonable. Since the task manager doesn’t display write activity, it’s unlikely actual data is being written.

Pages (3): Previous 1 2 3