rhl6u128

Lemur zaprasza

Red Hat® Linux 6 Unleashed

Chapter 14: Samba

Previous
ChapterNext
Chapter

Sections in this Chapter:

Installing
Samba

Optimizing Samba Performance

Common
smb.conf Configuration Options

Getting
a Simple Samba Setup Running

Testing
Your Configuration

Samba
Documentation Sources

Configuring
Samba

Running
the Samba Server

Using
SWAT for Web-Based Samba Configuration

Sharing
Files and Print Services

Accessing
Shares

Previous
SectionNext
Section

Optimizing Samba Performance
Samba performs
excellently, so performance
usually isn't an issue. If performance becomes an issue, there are several
options to evaluate.

Note -
The author tested all of the following Samba configuration performance
enhancement techniques and was unable to attain any significant performance
gains on an underloaded Samba server with a Celeron 333, 64MB of RAM, a 7200rpm
14.4GB disk, and 100Mb wiring, using a test of copying an 11MB file back and
forth. The conclusion is that gains depend on many factors, including but not
limited to system load. These techniques will not help if the bottleneck is the
wire, which appears to be the case on the author's
setup.

Samba's default for option wide
links= is yes. Setting it to
no gains some security benefits. However,
significant performance costs have been reported in certain environments. If you
have wide links= set to
no in heavy usage environments, you may want to
experiment with changing it to
yes.If
wide links= is set to
yes, further optimization may be gained by setting
getwd cache= to yes in
the [global] section. (The default is
no.)Tweaks to virtual
memory utilization may also improve Samba performance. Two tweaks specifically
have been documented.

Caution -
Do not attempt the following bdflush and
buffermem tweaks without first consulting and
understanding the contents of file
/usr/doc/kernel-doc-2.2.5/sysctl/vm.txt. Each of the
values are explained in that document. If that file does not exist, install the
kernel documentation RPM. It will have a name similar to
kernel-doc-2.2.5-15.i386.rpm.

echo "80 500 64 64 80 6000 6000 1884 2" >/proc/sys/vm/bdflush
echo "60 80 80" >/proc/sys/vm/buffermem

Some other possible enhancement techniques include faster
network hardware and wiring, a better server hard disk, more server memory, or a
server CPU upgrade.The bottom line is that
performance is bottleneck-limited, so to improve performance, it's
essential to locate the performance bottleneck. A performance enhancement plan
can be made once that's done. Until the bottleneck is located, speculation
makes little sense.
One of the best bottleneck analysis techniques is deliberately
slowing a suspected bottleneck. If system throughput slows by a similar proportion,
you've found a bottleneck. If system throughput slows only
slightly, continue looking.