Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Apr 2024 18:41:08 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 277992] mpr and possible trim issues
Message-ID:  <bug-277992-227-HO4ZQcgipz@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-277992-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-277992-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277992

--- Comment #10 from mike@sentex.net ---
Created attachment 250268
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D250268&action=
=3Dedit
write performance of the tests

starting at 16:00 on the graph, I sent a series of zfs send | zfs recv of t=
he
zfs data set and zfs destroy the copy. I pause for 120 seconds, then initia=
te a
manual trim zpool trim -w pool and then pause 120secs and then start again.=
  As
you can see the throughput is consistent on writes.  Then at 08:00 I restart
the test, but this time I dont do a trim after the zfs destroy.  If manages
about 3 times (the dataset is about a 1/3rd of the pool's capacity and then=
 the
writes become brutally slow which tracks FreeBSD.  If I then do a zpool tri=
m -w
pool, performance is back to normal.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



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