37 ms·

another data point: SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 30 Celsiu

by jrib 4y ago

another data point: SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 30 Celsius Available Spare: 100% Available Spare Threshold: 99% Percentage Used: 1% Data Units Read: 53,345,304 [27.3 TB] Data Units Written: 59,621,038 [30.5 TB] Host Read Commands: 349,163,066 Host Write Commands: 218,226,588 Controller Busy Time: 0 Power Cycles: 109 Power On Hours: 225 Unsafe Shutdowns: 8 Media and Data Integrity Errors: 0 Error Information Log Entries: 0 MacBook Air (M1, 2020) 16GB 512GB

cool_hw 4y ago
Your read/writes seem to be comparable to the parent, but your power on hours are significantly lower, really hard to draw any conclusions here. I wonder if this whole issue is simply MacOS dumping the stuff in memory to disk when going to standby, and then reading it all back. So for a 16GB machine, for simplicity, let's say you always have RAM saturated, and you open/close the lid 5 times in a day, you have 16GB * 5 = 80GB per day read/written. For 365 days, that is 80 * 365 = 29200 GB or 28.51 TB read/written.
- AdamJacobMuller 4y ago
  Launch day purchased M1 MacBook Pro with 4TB SSD. I have custom pmset setup to NOT dump to disk (mostly) with two aliases: pmset-fast: sudo pmset -ab hibernatemode 0 sleep 0 pmset-secure: sudo pmset -ab hibernatemode 25 sleep 0 displaysleep 1 First one is memory only, if the battery dies, the battery dies and the OS goes away. The second one is hard drive only, closing the lid writes to disk only and puts the laptop into deep sleep. I know I'm weird for having this but since I run the first one (fast) 99% of the time I can basically say I almost never write hibernation files to disk.
  - cool_hw 4y ago
    Thank you, this is useful. I think I'm going to try the memory only option. Your Read/Writes seem lower than others (still pretty high, but much better than other Apple Silicon)
  - cool_hw 4y ago
    Is there a noticeable difference in battery life usage with option 1?
- krackers 4y ago
  >open/close the lid 5 times in a day It's a bit smarter than that, it only writes memory contents to disk after a given period in standby. So in your example you'd only be incurring it twice a day probably.
  - cool_hw 4y ago
    Indeed, I intended to say letting it get to standby. :)

by jrib 4y ago

cool_hw 4y ago

Your read/writes seem to be comparable to the parent, but your power on hours are significantly lower, really hard to draw any conclusions here. I wonder if this whole issue is simply MacOS dumping the stuff in memory to disk when going to standby, and then reading it all back. So for a 16GB machine, for simplicity, let's say you always have RAM saturated, and you open/close the lid 5 times in a day, you have 16GB * 5 = 80GB per day read/written. For 365 days, that is 80 * 365 = 29200 GB or 28.51 TB read/written.

AdamJacobMuller 4y ago
Launch day purchased M1 MacBook Pro with 4TB SSD. I have custom pmset setup to NOT dump to disk (mostly) with two aliases: pmset-fast: sudo pmset -ab hibernatemode 0 sleep 0 pmset-secure: sudo pmset -ab hibernatemode 25 sleep 0 displaysleep 1 First one is memory only, if the battery dies, the battery dies and the OS goes away. The second one is hard drive only, closing the lid writes to disk only and puts the laptop into deep sleep. I know I'm weird for having this but since I run the first one (fast) 99% of the time I can basically say I almost never write hibernation files to disk.
- cool_hw 4y ago
  Thank you, this is useful. I think I'm going to try the memory only option. Your Read/Writes seem lower than others (still pretty high, but much better than other Apple Silicon)
- cool_hw 4y ago
  Is there a noticeable difference in battery life usage with option 1?
krackers 4y ago
>open/close the lid 5 times in a day It's a bit smarter than that, it only writes memory contents to disk after a given period in standby. So in your example you'd only be incurring it twice a day probably.
- cool_hw 4y ago
  Indeed, I intended to say letting it get to standby. :)