From 20967627378194121bc48bf387838b8bd7682478 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Mar 2003 16:48:14 +0000 Subject: Regenerate (This used to be commit 25db62e3101dbcae8e9daee3cb16430297afa223) --- docs/htmldocs/speed.html | 68 ++++++++++++++++++++++++------------------------ 1 file changed, 34 insertions(+), 34 deletions(-) (limited to 'docs/htmldocs/speed.html') diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html index c99a49142c..85863dcd5f 100644 --- a/docs/htmldocs/speed.html +++ b/docs/htmldocs/speed.html @@ -5,7 +5,7 @@ >Samba performance issuesChapter 19. Samba performance issuesChapter 18. Samba performance issues

19.1. Comparisons

18.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 @@ -111,9 +111,9 @@ CLASS="SECT1" >

19.2. Socket options

18.2. Socket options

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

19.3. Read size

18.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 @@ -165,9 +165,9 @@ CLASS="SECT1" >

19.4. Max xmit

18.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 @@ -188,9 +188,9 @@ CLASS="SECT1" >

19.5. Log level

18.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 @@ -202,9 +202,9 @@ CLASS="SECT1" >

19.6. Read raw

18.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, @@ -224,9 +224,9 @@ CLASS="SECT1" >

19.7. Write raw

18.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, @@ -241,9 +241,9 @@ CLASS="SECT1" >

19.8. Slow Clients

18.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).

19.9. Slow Logins

18.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 @@ -271,9 +271,9 @@ CLASS="SECT1" >

19.10. Client tuning

18.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 @@ -431,7 +431,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Creating Group ProfilesCreating Group Prolicy Files