summaryrefslogtreecommitdiff
path: root/docs/htmldocs/speed.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/htmldocs/speed.html')
-rw-r--r--docs/htmldocs/speed.html92
1 files changed, 46 insertions, 46 deletions
diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html
index 9df2a6d6af..85562e3e89 100644
--- a/docs/htmldocs/speed.html
+++ b/docs/htmldocs/speed.html
@@ -11,13 +11,13 @@ TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
-HREF="p1346.html"><LINK
+HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="Group mapping HOWTO"
HREF="groupmapping.html"><LINK
REL="NEXT"
TITLE="Appendixes"
-HREF="p3106.html"></HEAD
+HREF="appendixes.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -59,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="p3106.html"
+HREF="appendixes.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -74,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="SPEED"
></A
->Chapter 22. Samba performance issues</H1
+>Chapter 23. Samba performance issues</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN2982"
+NAME="AEN3065"
></A
->22.1. Comparisons</H1
+>23.1. Comparisons</H1
><P
>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,17 +111,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN2988"
+NAME="AEN3071"
></A
->22.2. Oplocks</H1
+>23.2. Oplocks</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN2990"
+NAME="AEN3073"
></A
->22.2.1. Overview</H2
+>23.2.1. Overview</H2
><P
>Oplocks are the way that SMB clients get permission from a server to
locally cache file operations. If a server grants an oplock
@@ -155,9 +155,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN2998"
+NAME="AEN3081"
></A
->22.2.2. Level2 Oplocks</H2
+>23.2.2. Level2 Oplocks</H2
><P
>With Samba 2.0.5 a new capability - level2 (read only) oplocks is
supported (although the option is off by default - see the smb.conf
@@ -179,9 +179,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN3004"
+NAME="AEN3087"
></A
->22.2.3. Old 'fake oplocks' option - deprecated</H2
+>23.2.3. Old 'fake oplocks' option - deprecated</H2
><P
>Samba can also fake oplocks, by granting a oplock whenever a client
asks for one. This is controlled using the smb.conf option "fake
@@ -200,9 +200,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3008"
+NAME="AEN3091"
></A
->22.3. Socket options</H1
+>23.3. Socket options</H1
><P
>There are a number of socket options that can greatly affect the
performance of a TCP based server like Samba.</P
@@ -228,9 +228,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3015"
+NAME="AEN3098"
></A
->22.4. Read size</H1
+>23.4. Read size</H1
><P
>The option "read size" affects the overlap of disk reads/writes with
network reads/writes. If the amount of data being transferred in
@@ -254,9 +254,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3020"
+NAME="AEN3103"
></A
->22.5. Max xmit</H1
+>23.5. Max xmit</H1
><P
>At startup the client and server negotiate a "maximum transmit" size,
which limits the size of nearly all SMB commands. You can set the
@@ -277,9 +277,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3025"
+NAME="AEN3108"
></A
->22.6. Locking</H1
+>23.6. Locking</H1
><P
>By default Samba does not implement strict locking on each read/write
call (although it did in previous versions). If you enable strict
@@ -294,9 +294,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3029"
+NAME="AEN3112"
></A
->22.7. Share modes</H1
+>23.7. Share modes</H1
><P
>Some people find that opening files is very slow. This is often
because of the "share modes" code needed to fully implement the dos
@@ -324,9 +324,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3034"
+NAME="AEN3117"
></A
->22.8. Log level</H1
+>23.8. Log level</H1
><P
>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
@@ -338,9 +338,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3037"
+NAME="AEN3120"
></A
->22.9. Wide lines</H1
+>23.9. Wide lines</H1
><P
>The "wide links" option is now enabled by default, but if you disable
it (for better security) then you may suffer a performance hit in
@@ -352,9 +352,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3040"
+NAME="AEN3123"
></A
->22.10. Read raw</H1
+>23.10. Read raw</H1
><P
>The "read raw" operation is designed to be an optimised, low-latency
file read operation. A server may choose to not support it,
@@ -374,9 +374,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3045"
+NAME="AEN3128"
></A
->22.11. Write raw</H1
+>23.11. Write raw</H1
><P
>The "write raw" operation is designed to be an optimised, low-latency
file write operation. A server may choose to not support it,
@@ -391,9 +391,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3049"
+NAME="AEN3132"
></A
->22.12. Read prediction</H1
+>23.12. Read prediction</H1
><P
>Samba can do read prediction on some of the SMB commands. Read
prediction means that Samba reads some extra data on the last file it
@@ -417,9 +417,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3056"
+NAME="AEN3139"
></A
->22.13. Memory mapping</H1
+>23.13. Memory mapping</H1
><P
>Samba supports reading files via memory mapping them. One some
machines this can give a large boost to performance, on others it
@@ -438,9 +438,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3061"
+NAME="AEN3144"
></A
->22.14. Slow Clients</H1
+>23.14. Slow Clients</H1
><P
>One person has reported that setting the protocol to COREPLUS rather
than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).</P
@@ -455,9 +455,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3065"
+NAME="AEN3148"
></A
->22.15. Slow Logins</H1
+>23.15. Slow Logins</H1
><P
>Slow logins are almost always due to the password checking time. Using
the lowest practical "password level" will improve things a lot. You
@@ -468,9 +468,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3068"
+NAME="AEN3151"
></A
->22.16. Client tuning</H1
+>23.16. Client tuning</H1
><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
@@ -572,9 +572,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3100"
+NAME="AEN3183"
></A
->22.17. My Results</H1
+>23.17. My Results</H1
><P
>Some people want to see real numbers in a document like this, so here
they are. I have a 486sx33 client running WfWg 3.11 with the 3.11b
@@ -631,7 +631,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="p3106.html"
+HREF="appendixes.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -647,7 +647,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
-HREF="p1346.html"
+HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD