Bug 142914 - [zfs] ZFS performance degradation over time
Summary: [zfs] ZFS performance degradation over time
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-fs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-17 18:00 UTC by miks.mikelsons
Modified: 2011-07-27 09:06 UTC (History)
0 users

See Also:


Attachments
ivoras.vcf (292 bytes, text/x-vcard; charset=utf-8)
2010-01-18 09:52 UTC, Ivan Voras
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description miks.mikelsons 2010-01-17 18:00:07 UTC
After migrating servers to from UFS to ZFS, we got constant file system
performance degradation in couple time by week.

System load has not been changed since migration to ZFS, so only reason
of this problems can be ZFS itself.

We had this problems on Intel server systems with 8GB and more RAM.  We
also tried to disable prefetch, but problem still existed.  Even with
latest FreeBSD 8.0 Stable we had same problem.

One solution to this problem is - stop all httpd, php-cgi and mysql
processes, wait 1-2 minutes and then start it again.  On other servers
we just migrated back to UFS and problem was gone.

One strange thing we noticed is - when server have performance problem,
"zpool iostat" is showing like this
"
pool         used  avail   read  write   read  write
----------  -----  -----  -----  -----  -----  -----
zroot        113G  26.1G     53    392  2.80M  20.3M
"

after processes restart:
"
pool         used  avail   read  write   read  write
----------  -----  -----  -----  -----  -----  -----
zroot       99.9G  39.1G      6     40   367K  1.12M

"

How can "used" value differ?
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2010-01-17 20:12:46 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 2 Ivan Voras 2010-01-18 09:52:04 UTC
RE: "used value differs": Have you checked with "du" the status "before" 
and "after" to rule out that something is actually allocating a big file?

There is a similar problem reported here:
http://permalink.gmane.org/gmane.os.freebsd.stable/66780
Comment 3 Martin Matuska freebsd_committer freebsd_triage 2011-07-18 12:57:00 UTC
Any news on this PR? Can we close it?
Is the problem still present with ZFS v28 and latest 8-STABLE or 9-CURRENT?

-- 
Martin Matuska
FreeBSD committer
http://blog.vx.sk
Comment 4 Martin Matuska freebsd_committer freebsd_triage 2011-07-27 09:06:30 UTC
State Changed
From-To: open->closed

Closed on submitter request.