1131
Defragged Zebra (sh.itjust.works)
submitted 2 years ago by to c/programmer_humor@programming.dev
51 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 2 years ago* (1 child)

Random reads are still slower than sequential in SSD. try torrenting for a year on SSD, then benchmark then defragment then benchmark. it will be very measureable difference. you may need some linux filesystem like XFS as im not sure if there is a way to defrag SSDs in windows.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago (1 child)

    That's because the drive was written to its limits; the defrag runs a TRIM command that safely releases and resets empty sectors. Random reads and sequential reads /on clean drives that are regularly TRIMmed/ are within random variance of each other.

    Source: ran large scale data collection for a data centre when SSDs were relatively new to the company so focused a lot on it, plus lots of data from various sectors since.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago* (last edited 2 years ago) (1 child)

    I'm pretty sure running XFS defrag will defrag without trimming no matter the type of block device.

    Edit: yea you might actually be right. I Played with my fstab too much years ago, and never thought of that untill now

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    I understood that XFS automatically mounted SSD's with XFS_XFLAG_NODEFRAG set? Is this not the case?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    yea you might actually be right. I Played with my fstab too much years ago, and never thought of that until now

    But does that flag affect manually running xfs_fsr?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago

    According to the man(8) page, it will avoid touching any blocks that have the chattr -f flag set, which is XSR_XFLAGS_NODEFRAG... So I think if the docs are still accurate to the code, yes.

    A lot of ifs in that assumption.

  • permalink
  • fedilink
  • source
  • parent