Personal computing discussed
Moderators: renee, morphine, Steel
derFunkenstein wrote:I might be totally wrong on this but looking at your screenshots it says your "OS is optimized for HDD". Could this mean that TRIM is not enabled? Does that have an impact on the number of writes? I'm curious what it says the optimizations would do.
just brew it! wrote:How much RAM do you have, and is your pagefile on the SSD?
Do you have hibernation enabled?
derFunkenstein wrote:I might be totally wrong on this but looking at your screenshots it says your "OS is optimized for HDD". Could this mean that TRIM is not enabled? Does that have an impact on the number of writes? I'm curious what it says the optimizations would do.
Klyith wrote:No, "OS Optimization" in the Samsung magician software is a terrible feature that does some really dumb "tweaks" -- for example setting the processor to run at 100% minimum in windows' power management options. No one should ever use it if they have a samsung drive, and after magician's performance in the SSD endurance test I'm skeptical of it's health indicators too. Though RAPID works much better than TR's review OTOH.
Klyith wrote:Trim can definitely have an impact on number of block written -- if trim is disabled the drive accumulates "dirty" blocks and these make write amplification happen as multiple blocks can get re-written for each original write. On non-sandforce drives trim is super important. The easiest way to check in W7 & up is to look in disk defragmenter and check that the SSD drive is greyed out. That means the os detected it as a ssd and should have auto-enabled trim and other ssd features.l
Klyith wrote:hbarnwheeler you should get CrystalDiskInfo and double check with that.
just brew it! wrote:Hmmm, let's do a little rough math. Assuming a full 16GB is written each time (I don't think that's the case unless the system is fully committed so the RAM is actually in use -- note that you can adjust the Hiberfile to be as little as 50% the size of your RAM), and ignoring the Gibi/Giga thing, 120TB of writes means that 16GB was written 7500 times. If the system has been running 20 months, that's 375 sleep events a month, which is more than 10 a day. Which I guess is possible if sleep is on a relatively short timeout. (Is that math right? I'm not through my first cup of coffee yet).Hybrid Sleep is almost certainly the issue. If I am understanding correctly how Hybrid Sleep works, you are writing 16GB of data to the SSD every time the system sleeps.
SuperSpy wrote:That might be possible if something is screwing with the machine's ability to stay asleep, like buggy wake on LAN or an overly-sensitive mouse.
just brew it! wrote:SuperSpy wrote:That might be possible if something is screwing with the machine's ability to stay asleep, like buggy wake on LAN or an overly-sensitive mouse.
Yeah, that's what I had in mind when I asked if sleep/hibernate events are logged.
Usacomp2k3 wrote:just brew it! wrote:SuperSpy wrote:That might be possible if something is screwing with the machine's ability to stay asleep, like buggy wake on LAN or an overly-sensitive mouse.
Yeah, that's what I had in mind when I asked if sleep/hibernate events are logged.
Source: "Power-troubleshooter" Event ID 1 is what logs the wake up/resume.
I've got logs on my work laptop for "Wake source: S4 Doze to Hybernate" and "wake source: power button". I believe the former was a hybrid sleep initiative.
hbarnwheeler wrote:Again, I don't know if it's enough to explain the 120TB total, but the new Opera really thrashes the disk. I set ProcMon to filter disk writes and I found this:
imgur-dot-com/ltWJONr
just brew it! wrote:hbarnwheeler wrote:Again, I don't know if it's enough to explain the 120TB total, but the new Opera really thrashes the disk. I set ProcMon to filter disk writes and I found this:
imgur-dot-com/ltWJONr
There's no way all of that is making it to the physical SSD, it must be mostly sitting in file cache. That's over a gig per second!
But if even a fraction of that is making it out to the drive, yeah that could certainly explain the 120TB, depending on how long this has been going on.
just brew it! wrote:There's no way all of that is making it to the physical SSD, it must be mostly sitting in file cache. That's over a gig per second!
But if even a fraction of that is making it out to the drive, yeah that could certainly explain the 120TB, depending on how long this has been going on.
hbarnwheeler wrote:FWIW: I get similar results when I leave Chrome sitting idle.
Klyith wrote:So when you were looking at Opera, was that stream of writes constant like that screenshot shows, for long periods of time? Chrome & Firefox on my system will also produce frequent blobs of writes for session info, but it happens in chunks every 5-15 seconds. If they are idle, it takes more like a full minute to accumulate a similar size list of writes to what you got in 1 second.
Klyith wrote:One question: was your windows install originally on a HD and get cloned to the SSD, or did you start with a fresh install?
just brew it! wrote:Hybrid Sleep is almost certainly the issue. If I am understanding correctly how Hybrid Sleep works, you are writing 16GB of data to the SSD every time the system sleeps.
Microsoft wrote:Should the pagefile be placed on SSDs?
Yes. Most pagefile operations are small random reads or larger sequential writes, both of which are types of operations that SSDs handle well.
In looking at telemetry data from thousands of traces and focusing on pagefile reads and writes, we find that
•Pagefile.sys reads outnumber pagefile.sys writes by about 40 to 1,
•Pagefile.sys read sizes are typically quite small, with 67% less than or equal to 4 KB, and 88% less than 16 KB.
•Pagefile.sys writes are relatively large, with 62% greater than or equal to 128 KB and 45% being exactly 1 MB in size.
In fact, given typical pagefile reference patterns and the favorable performance characteristics SSDs have on those patterns, there are few files better than the pagefile to place on an SSD.
Are there any concerns regarding the Hibernate file and SSDs?
No, hiberfile.sys is written to and read from sequentially and in large chunks, and thus can be placed on either HDDs or SSDs.
Ryu Connor wrote:just brew it! wrote:Hybrid Sleep is almost certainly the issue. If I am understanding correctly how Hybrid Sleep works, you are writing 16GB of data to the SSD every time the system sleeps.
No it doesn't. It at most uses 75% of the total RAM capacity and can even be forced down to 50% and those are just the sizes of the file. It does not use that entire capacity.
Also the Pagefile barely generates any writes at all.
just brew it! wrote:Yeah, I think we've already moved on from that theory. As noted a few posts back, it looks like Opera may be the culprit.