Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Ubuntu Aims To TRIM SSDs By Default

  1. #1
    Join Date
    Jan 2007
    Posts
    13,464

    Default Ubuntu Aims To TRIM SSDs By Default

    Phoronix: Ubuntu Aims To TRIM SSDs By Default

    During the first day of the latest virtual Ubuntu Developer Summit, Canonical developers plotted out the enabling of TRIM/DISCARD support by default for solid-state drives on Ubuntu...

    http://www.phoronix.com/vr.php?view=MTUxOTY

  2. #2
    Join Date
    Jul 2012
    Posts
    620

    Default

    Wow. About time ehh?

  3. #3
    Join Date
    Mar 2009
    Posts
    135

    Default

    Quote Originally Posted by blackout23 View Post
    Wow. About time ehh?
    Yeah... Windows 7 was released in 2009 with trim support?

  4. #4
    Join Date
    Oct 2011
    Posts
    65

    Default

    Quote Originally Posted by Ferdinand View Post
    Yeah... Windows 7 was released in 2009 with trim support?
    Problem is that on Windows 7, NTFS does what the discard option does on the various file-systems that support it. There are cases when fstrim / discard are not considered to be optimal.

  5. #5
    Join Date
    Dec 2008
    Posts
    145

    Default

    I did not listen to the whole conference, so I do not know if it was mentioned, but my understanding is that some SSDs are much slower than others at responding after large TRIM commands. I believe some of the people doing SSD flash longevity tests found that certain Sandforce SSDs could be slow for a minute or more after large TRIM commands.

  6. #6

    Default

    Quote Originally Posted by jwilliams View Post
    I did not listen to the whole conference, so I do not know if it was mentioned, but my understanding is that some SSDs are much slower than others at responding after large TRIM commands. I believe some of the people doing SSD flash longevity tests found that certain Sandforce SSDs could be slow for a minute or more after large TRIM commands.
    It may be due to Sandforce chips using in-house compression for the data it manipulates, therefore large TRIM commands means large compression/decompression processes.

  7. #7
    Join Date
    Dec 2007
    Posts
    139

    Default It should be part of the installer

    I am up to my fourth SSD and they all work fine with Arch and Debian. When I got my first one I read a whole lot of HowTos and stuff that are all pretty much way out of date. The modern installer disk partitioners do a perfectly good job of setting them up except for TRIM.

    Why not another dialog to activate TRIM? As in Mount Point, Bootable, Trim etc. It has always seemed silly that you have to manually edit fstab to put in "discard", when TRIM has been supported for many years.

    Off topic but related, Techradar are doing a long term test of SSDs by hammering them all day long. It is very interesting that even after 200Tb of data being written and deleted they are all still fully functional, although some are using a few replacement addresses.

  8. #8
    Join Date
    Dec 2007
    Posts
    139

    Default That should have been The Tech Report


  9. #9
    Join Date
    Dec 2008
    Posts
    145

    Default

    That techreport SSD longevity test has the same flaw as most others that have been done since this has become trendy. The problem is that they are not testing data retention time. The main reason that the flash in consumer SSDs is specified as having 3000 erase cycles (or whatever number is given) is that once you go beyond that number of erase cycles, the data retention time could fall below 1 year (which is the minimum allowed data retention spec for consumer flash).

    To test data retention, you have to stop writing (and have recorded the checksums of the last data written), leave the SSD powered off for some time (obviously a year is not practical, but I think at least a week would be a minimum practical time for testing), and then power up the SSD and verify the checksums on the data.

    With the test techreport has been doing, the data retention time could get down as low as a few hours and they would not even know it. They would think the SSD was still functioning. But very few users would even consider using an SSD with a data retention time of less than 24 hours. Personally, I would not use one with a data retention time of less than a month.

  10. #10
    Join Date
    Jul 2012
    Posts
    620

    Default

    Quote Originally Posted by grege View Post
    I am up to my fourth SSD and they all work fine with Arch and Debian. When I got my first one I read a whole lot of HowTos and stuff that are all pretty much way out of date. The modern installer disk partitioners do a perfectly good job of setting them up except for TRIM.

    Why not another dialog to activate TRIM? As in Mount Point, Bootable, Trim etc. It has always seemed silly that you have to manually edit fstab to put in "discard", when TRIM has been supported for many years.

    Off topic but related, Techradar are doing a long term test of SSDs by hammering them all day long. It is very interesting that even after 200Tb of data being written and deleted they are all still fully functional, although some are using a few replacement addresses.
    200TB is nothing. SSDs can take over 1500TB of write performance.

    http://www.xtremesystems.org/forums/...e-25nm-Vs-34nm

    You are basically never going to write your SSD to death.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •