FOSSology Project Logo FOSSology
Advancing open source analysis and development
 

Differences

This shows you the differences between the selected revision and the current version of the page.

nfs_performance_investigation 2010/07/29 05:44 nfs_performance_investigation 2010/08/12 20:17 current
Line 62: Line 62:
    * In my base test sytem: default is 8     * In my base test sytem: default is 8
    * Change to small and to large (4, 16, 32, 128), DD test no more changes     * Change to small and to large (4, 16, 32, 128), DD test no more changes
 +==== Third phase NFS performance investigation ====
 +=== Test Environment ===
 +Hardware:
 +  *bl480c-1.test  (CPU: 2xQuad-Core Intel Xeon, 3.00GHz MEM: 12x2GB)  web/db/scheduler
 +  *bl460c-9.test  (CPU: 2xMulti-Core Intel Xeon, 2.33GHZ MEM: 4x1GB)  agent
 +  *bl460c-13.test (CPU: 1xMulti-Core Intel Xeon, 3.00GHZ MEM: 4x1GB)  agent
 +  *bl460c-15.test (CPU: 1xMulti-Core Intel Xeon, 3.00GHZ MEM: 4x1GB)  agent
 +  *bl460c-10.test (CPU: 2xMulti-Core Intel Xeon, 2.33GHZ MEM: 4x1GB)  nfs server
 +Test Data:
 +  *SLES-11-SP1-DVD-x86_64-GMC3-DVD1.iso    2.9G
 +  *SLES-11-SP1-DVD-x86_64-GMC3-DVD2.iso    4.3G
 +  *SLES-11-SP1-DVD-x86_64-GMC3-DVD3.iso    2.7G
 +Test Case:
 +  - Current corss mount system: Using UI upload 3 isos as close as together, only queue nomos job.
 +  - 1 dedicated NFS server use single nfs mount: Using UI upload 3 isos as close as together, only queue nomos job.
 +  - 1 dedicated NFS server use single nfs mount, increase nfs server memory from 4G to 8G: Using UI upload 3 isos as close as together, didn't finished all nomos job.
 +=== Test Results ===
 +{{:nfs_result.jpg|}}
===== NFS configuration Recommendations ===== ===== NFS configuration Recommendations =====
So based on above investigation and testing, i have follow recommendations for multiple FOSSology setup: So based on above investigation and testing, i have follow recommendations for multiple FOSSology setup:
-  - Use single NFS server to instead of cross mount NFS, also suggest the NFS server don't run other things db/web/scheduler/agent+  - If you have a amazing server with large memory, i recommend use single NFS server with large memory to instead of cross mount NFS, also suggest the NFS server don't run other things db/web/scheduler/agent
 +    Otherwise cross mount configuration NFS will be our prefer.
  - About NFS client mount options   - About NFS client mount options
    * Modern Linux clients mostly have good defaults, most mount options you specify will make things worse     * Modern Linux clients mostly have good defaults, most mount options you specify will make things worse
 
nfs_performance_investigation.1280403875.txt.gz · Last modified: 2010/07/29 05:44 by vincent

Copyright (C) 2007-2009 Hewlett-Packard Development Company, L.P.
FOSSology Project documentation is licensed under the GNU Free Documentation License Version 1.2
Recent changes RSS feed Valid XHTML 1.0 Valid CSS3 Driven by DokuWiki