Bug 70080
Summary: | high load NFS performance | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <aander07> |
Component: | kernel | Assignee: | Steve Dickson <steved> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | k.georgiou, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-01-12 12:34:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2002-07-30 03:10:22 UTC
I have also tested 2.4.18-5, and the maximum performance under that kernel is around 30Mb/s. The long waits for stat() and friends did not show up, but that could just be a result of the server not handling as much traffic because of the new upper performance limits in 2.4.18-5. I have also observed 2 of the 4 hosts that I have installed it on have had processes go into device wait and not recover, but new processes have no problems accessing the same NFS mount point. One of the hosts has 1G of RAM, the other host has 2G of RAM. 2.4.18-17.7.x still exhibits the same device wait behavior as 2.4.18-5 and 2.4.18-10 did. How did you generate the "high NFS I/O loads"? How did you get these numbers (1300-1800 NFS ops/sec, >20Mbytes/sec I/O)? |