diff options
Diffstat (limited to 'docs/htmldocs/Samba3-HOWTO/speed.html')
| -rw-r--r-- | docs/htmldocs/Samba3-HOWTO/speed.html | 54 |
1 files changed, 27 insertions, 27 deletions
diff --git a/docs/htmldocs/Samba3-HOWTO/speed.html b/docs/htmldocs/Samba3-HOWTO/speed.html index 90643035ed..9abb652d7b 100644 --- a/docs/htmldocs/Samba3-HOWTO/speed.html +++ b/docs/htmldocs/Samba3-HOWTO/speed.html @@ -1,4 +1,4 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 45. Samba Performance Tuning</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part VI. Reference Section"><link rel="prev" href="Other-Clients.html" title="Chapter 44. Samba and Other CIFS Clients"><link rel="next" href="ch-ldap-tls.html" title="Chapter 46. LDAP and Transport Layer Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 45. Samba Performance Tuning</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Other-Clients.html">Prev</a> </td><th width="60%" align="center">Part VI. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="ch-ldap-tls.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 45. Samba Performance Tuning"><div class="titlepage"><div><div><h2 class="title"><a name="speed"></a>Chapter 45. Samba Performance Tuning</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="surname">Cochrane</span></h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:paulc@dth.scot.nhs.uk">paulc@dth.scot.nhs.uk</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="speed.html#id452209">Comparisons</a></span></dt><dt><span class="sect1"><a href="speed.html#id452238">Socket Options</a></span></dt><dt><span class="sect1"><a href="speed.html#id452323">Read Size</a></span></dt><dt><span class="sect1"><a href="speed.html#id452360">Max Xmit</a></span></dt><dt><span class="sect1"><a href="speed.html#id452401">Log Level</a></span></dt><dt><span class="sect1"><a href="speed.html#id452424">Read Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id452484">Write Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id452532">Slow Logins</a></span></dt><dt><span class="sect1"><a href="speed.html#id452554">Client Tuning</a></span></dt><dt><span class="sect1"><a href="speed.html#id452572">Samba Performance Problem Due to Changing Linux Kernel</a></span></dt><dt><span class="sect1"><a href="speed.html#id452655">Corrupt tdb Files</a></span></dt><dt><span class="sect1"><a href="speed.html#id452744">Samba Performance is Very Slow</a></span></dt></dl></div><div class="sect1" title="Comparisons"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452209"></a>Comparisons</h2></div></div></div><p> +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 45. Samba Performance Tuning</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part VI. Reference Section"><link rel="prev" href="Other-Clients.html" title="Chapter 44. Samba and Other CIFS Clients"><link rel="next" href="ch-ldap-tls.html" title="Chapter 46. LDAP and Transport Layer Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 45. Samba Performance Tuning</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Other-Clients.html">Prev</a> </td><th width="60%" align="center">Part VI. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="ch-ldap-tls.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 45. Samba Performance Tuning"><div class="titlepage"><div><div><h2 class="title"><a name="speed"></a>Chapter 45. Samba Performance Tuning</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="surname">Cochrane</span></h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:paulc@dth.scot.nhs.uk">paulc@dth.scot.nhs.uk</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="speed.html#id452214">Comparisons</a></span></dt><dt><span class="sect1"><a href="speed.html#id452243">Socket Options</a></span></dt><dt><span class="sect1"><a href="speed.html#id452328">Read Size</a></span></dt><dt><span class="sect1"><a href="speed.html#id452364">Max Xmit</a></span></dt><dt><span class="sect1"><a href="speed.html#id452406">Log Level</a></span></dt><dt><span class="sect1"><a href="speed.html#id452428">Read Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id452488">Write Raw</a></span></dt><dt><span class="sect1"><a href="speed.html#id452536">Slow Logins</a></span></dt><dt><span class="sect1"><a href="speed.html#id452558">Client Tuning</a></span></dt><dt><span class="sect1"><a href="speed.html#id452577">Samba Performance Problem Due to Changing Linux Kernel</a></span></dt><dt><span class="sect1"><a href="speed.html#id452660">Corrupt tdb Files</a></span></dt><dt><span class="sect1"><a href="speed.html#id452749">Samba Performance is Very Slow</a></span></dt></dl></div><div class="sect1" title="Comparisons"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452214"></a>Comparisons</h2></div></div></div><p> The Samba server uses TCP to talk to the client, so if you are trying to see if it performs well, you should really compare it to programs that use the same protocol. The most readily available @@ -20,7 +20,7 @@ suspect the biggest factor is not Samba versus some other system, but the hardware and drivers used on the various systems. Given similar hardware, Samba should certainly be competitive in speed with other systems. -</p></div><div class="sect1" title="Socket Options"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452238"></a>Socket Options</h2></div></div></div><p> +</p></div><div class="sect1" title="Socket Options"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452243"></a>Socket Options</h2></div></div></div><p> There are a number of socket options that can greatly affect the performance of a TCP-based server like Samba. </p><p> @@ -44,7 +44,7 @@ There have been reports that setting <em class="parameter"><code>socket options can seriously degrade Samba performance on the loopback adaptor (IP Address 127.0.0.1). It is strongly recommended that before specifying any settings for <em class="parameter"><code>socket options</code></em>, the effect first be quantitatively measured on the server being configured. -</p></div><div class="sect1" title="Read Size"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452323"></a>Read Size</h2></div></div></div><p> +</p></div><div class="sect1" title="Read Size"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452328"></a>Read Size</h2></div></div></div><p> The option <a class="link" href="smb.conf.5.html#READSIZE" target="_top">read size</a> affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in several of the SMB commands (currently SMBwrite, SMBwriteX, and @@ -61,7 +61,7 @@ The default value is 16384, but little experimentation has been done as yet to determine the optimal value, and it is likely that the best value will vary greatly between systems anyway. A value over 65536 is pointless and will cause you to allocate memory unnecessarily. -</p></div><div class="sect1" title="Max Xmit"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452360"></a>Max Xmit</h2></div></div></div><p> +</p></div><div class="sect1" title="Max Xmit"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452364"></a>Max Xmit</h2></div></div></div><p> At startup the client and server negotiate a <em class="parameter"><code>maximum transmit</code></em> size, which limits the size of nearly all SMB commands. You can set the maximum size that Samba will negotiate using the <a class="link" href="smb.conf.5.html#MAXXMIT" target="_top">max xmit</a> option @@ -74,12 +74,12 @@ It defaults to 65536 bytes (the maximum), but it is possible that some clients may perform better with a smaller transmit unit. Trying values of less than 2048 is likely to cause severe problems. In most cases the default is the best option. -</p></div><div class="sect1" title="Log Level"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452401"></a>Log Level</h2></div></div></div><p> +</p></div><div class="sect1" title="Log Level"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452406"></a>Log Level</h2></div></div></div><p> If you set the log level (also known as <a class="link" href="smb.conf.5.html#DEBUGLEVEL" target="_top">debug level</a>) higher than 2, then you may suffer a large drop in performance. This is because the server flushes the log file after each operation, which can be quite expensive. -</p></div><div class="sect1" title="Read Raw"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452424"></a>Read Raw</h2></div></div></div><p> +</p></div><div class="sect1" title="Read Raw"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452428"></a>Read Raw</h2></div></div></div><p> The <a class="link" href="smb.conf.5.html#READRAW" target="_top">read raw</a> operation is designed to be an optimized, low-latency file read operation. A server may choose to not support it, however, and Samba makes support for <a class="link" href="smb.conf.5.html#READRAW" target="_top">read raw</a> optional, with it @@ -90,26 +90,26 @@ get lower performance using it than they get using the conventional read operations, so you might like to try <a class="link" href="smb.conf.5.html#READRAW" target="_top">read raw = no</a> and see what happens on your network. It might lower, raise, or not affect your performance. Only testing can really tell. -</p></div><div class="sect1" title="Write Raw"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452484"></a>Write Raw</h2></div></div></div><p> +</p></div><div class="sect1" title="Write Raw"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452488"></a>Write Raw</h2></div></div></div><p> The <a class="link" href="smb.conf.5.html#WRITERAW" target="_top">write raw</a> operation is designed to be an optimized, low-latency file write operation. A server may choose to not support it, however, and Samba makes support for <a class="link" href="smb.conf.5.html#WRITERAW" target="_top">write raw</a> optional, with it being enabled by default. </p><p> Some machines may find <a class="link" href="smb.conf.5.html#WRITERAW" target="_top">write raw</a> slower than normal write, in which case you may wish to change this option. -</p></div><div class="sect1" title="Slow Logins"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452532"></a>Slow Logins</h2></div></div></div><p> +</p></div><div class="sect1" title="Slow Logins"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452536"></a>Slow Logins</h2></div></div></div><p> Slow logins are almost always due to the password checking time. Using the lowest practical <a class="link" href="smb.conf.5.html#PASSWORDLEVEL" target="_top">password level</a> will improve things. -</p></div><div class="sect1" title="Client Tuning"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452554"></a>Client Tuning</h2></div></div></div><p> +</p></div><div class="sect1" title="Client Tuning"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452558"></a>Client Tuning</h2></div></div></div><p> Often a speed problem can be traced to the client. The client (for example Windows for Workgroups) can often be tuned for better TCP performance. Check the sections on the various clients in <a class="link" href="Other-Clients.html" title="Chapter 44. Samba and Other CIFS Clients">Samba and Other CIFS Clients</a>. -</p></div><div class="sect1" title="Samba Performance Problem Due to Changing Linux Kernel"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452572"></a>Samba Performance Problem Due to Changing Linux Kernel</h2></div></div></div><p> +</p></div><div class="sect1" title="Samba Performance Problem Due to Changing Linux Kernel"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452577"></a>Samba Performance Problem Due to Changing Linux Kernel</h2></div></div></div><p> A user wrote the following to the mailing list: </p><div class="blockquote"><blockquote class="blockquote"><p> -<a class="indexterm" name="id452586"></a> -<a class="indexterm" name="id452593"></a> +<a class="indexterm" name="id452591"></a> +<a class="indexterm" name="id452597"></a> I am running Gentoo on my server and Samba 2.2.8a. Recently I changed kernel versions from <code class="filename">linux-2.4.19-gentoo-r10</code> to <code class="filename">linux-2.4.20-wolk4.0s</code>. Now I have a performance issue with Samba. Many of you will probably say, <span class="quote">“<span class="quote">Move to vanilla sources!</span>”</span> Well, I @@ -120,16 +120,16 @@ server and Windows, and it is terribly slow. </p></blockquote></div><p> The answer he was given is: </p><div class="blockquote"><blockquote class="blockquote"><p> -<a class="indexterm" name="id452629"></a> -<a class="indexterm" name="id452636"></a> -<a class="indexterm" name="id452643"></a> +<a class="indexterm" name="id452634"></a> +<a class="indexterm" name="id452641"></a> +<a class="indexterm" name="id452647"></a> Grab the mii-tool and check the duplex settings on the NIC. My guess is that it is a link layer issue, not an application layer problem. Also run ifconfig and verify that the framing error, collisions, and so on, look normal for ethernet. -</p></blockquote></div></div><div class="sect1" title="Corrupt tdb Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452655"></a>Corrupt tdb Files</h2></div></div></div><p> -<a class="indexterm" name="id452662"></a> -<a class="indexterm" name="id452669"></a> -<a class="indexterm" name="id452676"></a> +</p></blockquote></div></div><div class="sect1" title="Corrupt tdb Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452660"></a>Corrupt tdb Files</h2></div></div></div><p> +<a class="indexterm" name="id452667"></a> +<a class="indexterm" name="id452674"></a> +<a class="indexterm" name="id452681"></a> Our Samba PDC server has been hosting three TB of data to our 500+ users [Windows NT/XP] for the last three years using Samba without a problem. Today all shares went very slow. Also, the main smbd kept spawning new processes, so we had 1600+ running SMDB's (normally we average 250). It crashed the SUN E3500 cluster twice. @@ -138,28 +138,28 @@ After a lot of searching, I decided to <code class="literal">rm /var/locks/*.tdb <span class="emphasis"><em>Question:</em></span> Is there any method of keeping the *.tdb files in top condition, or how can I detect early corruption? </p><p> -<a class="indexterm" name="id452703"></a> -<a class="indexterm" name="id452710"></a> +<a class="indexterm" name="id452708"></a> +<a class="indexterm" name="id452714"></a> <span class="emphasis"><em>Answer:</em></span> Yes, run <code class="literal">tdbbackup</code> each time after stopping nmbd and before starting nmbd. </p><p> <span class="emphasis"><em>Question:</em></span> What I also would like to mention is that the service latency seems a lot lower than before the locks cleanup. Any ideas on keeping it top notch? </p><p> <span class="emphasis"><em>Answer:</em></span> Yes. Same answer as for previous question! -</p></div><div class="sect1" title="Samba Performance is Very Slow"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452744"></a>Samba Performance is Very Slow</h2></div></div></div><p> -<a class="indexterm" name="id452752"></a> +</p></div><div class="sect1" title="Samba Performance is Very Slow"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id452749"></a>Samba Performance is Very Slow</h2></div></div></div><p> +<a class="indexterm" name="id452756"></a> A site reported experiencing very baffling symptoms with MYOB Premier opening and accessing its data files. Some operations on the file would take between 40 and 45 seconds. </p><p> -<a class="indexterm" name="id452763"></a> -<a class="indexterm" name="id452770"></a> +<a class="indexterm" name="id452768"></a> +<a class="indexterm" name="id452775"></a> It turned out that the printer monitor program running on the Windows clients was causing the problems. From the logs, we saw activity coming through with pauses of about 1 second. </p><p> -<a class="indexterm" name="id452782"></a> -<a class="indexterm" name="id452788"></a> +<a class="indexterm" name="id452786"></a> +<a class="indexterm" name="id452793"></a> Stopping the monitor software resulted in the networks access at normal (quick) speed. Restarting the program caused the speed to slow down again. The printer was a Canon LBP-810 and the relevant task was |