From ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Feb 2003 22:14:04 +0000 Subject: Regenerate (This used to be commit 1ab5a3b17feb677425bb1071357c3dbabcc46c7e) --- docs/htmldocs/speed.html | 57 +++++++++++++++++++++++++++++++++--------------- 1 file changed, 39 insertions(+), 18 deletions(-) (limited to 'docs/htmldocs/speed.html') diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html index 1a05706f92..c99a49142c 100644 --- a/docs/htmldocs/speed.html +++ b/docs/htmldocs/speed.html @@ -5,8 +5,7 @@ >Samba performance issuesNext

Chapter 22. Samba performance issues

Chapter 19. Samba performance issues

22.1. Comparisons

19.1. Comparisons

The Samba server uses TCP to talk to the client. Thus if you are trying to see if it performs well you should really compare it to @@ -108,7 +111,9 @@ CLASS="SECT1" >

22.2. Socket options

19.2. Socket options

There are a number of socket options that can greatly affect the performance of a TCP based server like Samba.

22.3. Read size

19.3. Read size

The option "read size" affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in @@ -158,7 +165,9 @@ CLASS="SECT1" >

22.4. Max xmit

19.4. Max xmit

At startup the client and server negotiate a "maximum transmit" size, which limits the size of nearly all SMB commands. You can set the @@ -179,7 +188,9 @@ CLASS="SECT1" >

22.5. Log level

19.5. Log level

If you set the log level (also known as "debug level") higher than 2 then you may suffer a large drop in performance. This is because the @@ -191,7 +202,9 @@ CLASS="SECT1" >

22.6. Read raw

19.6. Read raw

The "read raw" operation is designed to be an optimised, low-latency file read operation. A server may choose to not support it, @@ -211,7 +224,9 @@ CLASS="SECT1" >

22.7. Write raw

19.7. Write raw

The "write raw" operation is designed to be an optimised, low-latency file write operation. A server may choose to not support it, @@ -226,7 +241,9 @@ CLASS="SECT1" >

22.8. Slow Clients

19.8. Slow Clients

One person has reported that setting the protocol to COREPLUS rather than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).

22.9. Slow Logins

19.9. Slow Logins

Slow logins are almost always due to the password checking time. Using the lowest practical "password level" will improve things a lot. You @@ -252,7 +271,9 @@ CLASS="SECT1" >

22.10. Client tuning

19.10. Client tuning

Often a speed problem can be traced to the client. The client (for example Windows for Workgroups) can often be tuned for better TCP @@ -386,7 +407,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" >NextAppendixesCreating Group Profiles