Attachment 23843 Details for Bug 40907 – tuning.7.diff

[patch] tuning.7.diff

tuning.7.diff (text/plain), 4.83 KB, created by Chris Pepper on 2002-07-23 02:50:01 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Chris Pepper

Created: 2002-07-23 02:50:01 UTC

Size: 4.83 KB

patch

obsolete

>--- tuning.7	Tue Jun 18 22:59:48 2002
>+++ tuning.7.fixed	Wed Jun 19 00:01:04 2002
>@@ -223,7 +223,7 @@
> .Dq Li "newfs -f 1024 -b 8192 ..." .
> .Pp
> If a large partition is intended to be used to hold fewer, larger files, such
>-as a database files, you can increase the
>+as database files, you can increase the
> .Em bytes/inode
> ratio which reduces the number of inodes (maximum number of files and
> directories that can be created) for that partition.
>@@ -273,7 +273,7 @@
> aware of.
> First, softupdates guarantees filesystem consistency in the
> case of a crash but could very easily be several seconds (even a minute!)
>-behind updating the physical disk.
>+behind on pending writes to the physical disk.
> If you crash you may lose more work
> than otherwise.
> Secondly, softupdates delays the freeing of filesystem
>@@ -288,7 +288,7 @@
> options exist that can help you tune the system.
> The most obvious and most dangerous one is
> .Cm async .
>-Don't ever use it, it is far too dangerous.
>+Don't ever use it; it is far too dangerous.
> A less dangerous and more
> useful
> .Xr mount 8
>@@ -425,7 +425,7 @@
> .Va net.inet.tcp.recvspace
> sysctls are of particular interest if you are running network intensive
> applications.
>-This controls the amount of send and receive buffer space
>+They control the amount of send and receive buffer space
> allowed for any given TCP connection.
> The default sending buffer is 32K; the default receiving buffer
> is 64K.
>@@ -442,7 +442,7 @@
> You can adjust the buffer size for incoming and outgoing data separately.
> For example, if your machine is primarily doing web serving you may want
> to decrease the recvspace in order to be able to increase the
>-sendspace without eating too much kernel memory.
>+sendspace without using too much kernel memory.
> Note that the routing table (see
> .Xr route 8 )
> can be used to introduce route-specific send and receive buffer size
>@@ -469,7 +469,7 @@
> .Va net.inet.tcp.rfc1323
> sysctl.
> These extensions should be enabled and the TCP buffer size should be set
>-to a value larger than 65536 in order to obtain good performance out of
>+to a value larger than 65536 in order to obtain good performance from
> certain types of network links; specifically, gigabit WAN links and
> high-latency satellite links.
> RFC1323 support is enabled by default.
>@@ -577,7 +577,7 @@
> You can do a simple calculation to figure out how many you need.
> If you have a web server which maxes out at 1000 simultaneous connections,
> and each connection eats a 16K receive and 16K send buffer, you need
>-approximate 32MB worth of network buffers to deal with it.
>+approximately 32MB worth of network buffers to deal with it.
> A good rule of
> thumb is to multiply by 2, so 32MBx2 = 64MB/2K = 32768.
> So for this case
>@@ -619,7 +619,7 @@
> circumstances.
> .Sh KERNEL CONFIG TUNING
> There are a number of kernel options that you may have to fiddle with in
>-a large scale system.
>+a large-scale system.
> In order to change these options you need to be
> able to compile a new kernel from source.
> The
>@@ -661,11 +661,11 @@
> to boot without those options.
> If it works, great!
> The operating system
>-will be able to better-use higher-end CPU features for MMU, task switching,
>+will be able to better use higher-end CPU features for MMU, task switching,
> timebase, and even device operations.
> Additionally, higher-end CPUs support
>-4MB MMU pages which the kernel uses to map the kernel itself into memory,
>-which increases its efficiency under heavy syscall loads.
>+4MB MMU pages, which the kernel uses to map the kernel itself into memory,
>+increasing its efficiency under heavy syscall loads.
> .Sh IDE WRITE CACHING
> .Fx 4.3
> flirted with turning off IDE write caching.
>@@ -676,8 +676,8 @@
> IDE drives lie about when a write completes.
> With IDE write caching turned
> on, IDE hard drives will not only write data to disk out of order, they
>-will sometimes delay some of the blocks indefinitely when under heavy disk
>-loads.
>+will sometimes delay some of the blocks indefinitely under heavy disk
>+load.
> A crash or power failure can result in serious filesystem
> corruption.
> So our default was changed to be safe.
>@@ -692,8 +692,9 @@
> on by setting the
> .Va hw.ata.wc
> loader tunable to 1.
>-More information on tuning the ATA driver system may be found in
>-.Xr ata 4.
>+More information on tuning the ATA driver system may be found in the
>+.Xr ata 4
>+man page.
> .Pp
> There is a new experimental feature for IDE hard drives called
> .Va hw.ata.tags
>@@ -747,7 +748,7 @@
> than 10BaseT, or use 1000BaseT rather then 100BaseT, depending on your needs.
> Most bottlenecks occur at the WAN link (e.g.\&
> modem, T1, DSL, whatever).
>-If expanding the link is not an option it may be possible to use
>+If expanding the link is not an option it may be possible to use the
> .Xr dummynet 4
> feature to implement peak shaving or other forms of traffic shaping to
> prevent the overloaded service (such as web services) from affecting other

Actions: View | Diff

Attachments on bug 40907: 23843