Skip site navigation (1)Skip section navigation (2)
In-Reply-To: <CANCZdfqx_vhNb2BukbM0bxrf8NH_9sXPKW%2BUf=LdoXjw_2w=Dg@mail.gmail.com>

| previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------EL2hQbxvGZPICZTUMLYILZPQ
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 5/2/2024 10:16 AM, Warner Losh wrote:
>
> When trims are fast, you want to send them to the drive as soon as you
> know the blocks are freed. UFS always does this (if trim is enabled at 
> all).
> ZFS has a lot of knobs to control when / how / if this is done.
>
> vfs.zfs.vdev.trim_min_active: 1
> vfs.zfs.vdev.trim_max_active: 2
> vfs.zfs.trim.queue_limit: 10
> vfs.zfs.trim.txg_batch: 32
> vfs.zfs.trim.metaslab_skip: 0
> vfs.zfs.trim.extent_bytes_min: 32768
> vfs.zfs.trim.extent_bytes_max: 134217728
> vfs.zfs.l2arc.trim_ahead: 0
>
> I've not tried to tune these in the past, but you can see how they affect things.
>
Thanks Warner, I will try and play around with these values to see if 
they impact things.  BTW, do you know what / why things would be 
"skipped" during trim events ?

kstat.zfs.zrootoffs.misc.iostats.trim_bytes_failed: 0
kstat.zfs.zrootoffs.misc.iostats.trim_extents_failed: 0
kstat.zfs.zrootoffs.misc.iostats.trim_bytes_skipped: 5968330752
kstat.zfs.zrootoffs.misc.iostats.trim_extents_skipped: 503986
kstat.zfs.zrootoffs.misc.iostats.trim_bytes_written: 181593186304
kstat.zfs.zrootoffs.misc.iostats.trim_extents_written: 303115


--------------EL2hQbxvGZPICZTUMLYILZPQ
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 5/2/2024 10:16 AM, Warner Losh
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CANCZdfqx_vhNb2BukbM0bxrf8NH_9sXPKW+Uf=LdoXjw_2w=Dg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div class="gmail_quote"><br>
          <div>When trims are fast, you want to send them to the drive
            as soon as you</div>
          <div>know the blocks are freed. UFS always does this (if trim
            is enabled at all).</div>
          <div>ZFS has a lot of knobs to control when / how / if this is
            done.</div>
          <div><br>
          </div>
          <div>
            <pre id="gmail-line1">vfs.zfs.vdev.trim_min_active: 1
vfs.zfs.vdev.trim_max_active: 2
vfs.zfs.trim.queue_limit: 10
vfs.zfs.trim.txg_batch: 32
vfs.zfs.trim.metaslab_skip: 0
vfs.zfs.trim.extent_bytes_min: 32768
vfs.zfs.trim.extent_bytes_max: 134217728
vfs.zfs.l2arc.trim_ahead: 0

</pre>
            <pre id="gmail-line1">I've not tried to tune these in the past, but you can see how they affect things.
</pre>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <p>Thanks Warner, I will try and play around with these values to
      see if they impact things.  BTW, do you know what / why things
      would be "skipped" during trim events ?</p>
    <p>kstat.zfs.zrootoffs.misc.iostats.trim_bytes_failed: 0<br>
      kstat.zfs.zrootoffs.misc.iostats.trim_extents_failed: 0<br>
      kstat.zfs.zrootoffs.misc.iostats.trim_bytes_skipped: 5968330752<br>
      kstat.zfs.zrootoffs.misc.iostats.trim_extents_skipped: 503986<br>
      kstat.zfs.zrootoffs.misc.iostats.trim_bytes_written: 181593186304<br>
      kstat.zfs.zrootoffs.misc.iostats.trim_extents_written: 303115<br>
    </p>
    <p><br>
    </p>
  </body>
</html>

--------------EL2hQbxvGZPICZTUMLYILZPQ--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>