Deleted Added
full compact
5c5
< .\" $FreeBSD: head/share/man/man7/tuning.7 102582 2002-08-29 20:34:06Z dillon $
---
> .\" $FreeBSD: head/share/man/man7/tuning.7 107383 2002-11-29 11:39:20Z ru $
109,110c109,112
< So it makes sense to have just one temporary directory and
< softlink to it from the other tmp directory locations.
---
> So it makes sense to have just one temporary directory and
> softlink to it from the other
> .Pa tmp
> directory locations.
275c277
< case of a crash but could very easily be several seconds (even a minute!)
---
> case of a crash but could very easily be several seconds (even a minute!\&)
286c288,289
< during a typical install. There is no loss of performance since the root
---
> during a typical install.
> There is no loss of performance since the root
528c531,532
< TCP feature is largly misunderstood. Historically speaking this feature
---
> TCP feature is largly misunderstood.
> Historically speaking, this feature
530c534,535
< along with the response. For example, when you type over a remote shell
---
> along with the response.
> For example, when you type over a remote shell,
532,537c537,546
< data representing the echo of the character. With delayed acks turned off
< the acknowledgement may be sent in its own packet before the remote service
< has a chance to echo the data it just received. This same concept also
< applies to any interactive protocol (e.g. SMTP, WWW, POP3) and can cut the
< number of tiny packets flowing across the network in half. The FreeBSD
< delayed-ack implementation also follows the TCP protocol rule that
---
> data representing the echo of the character.
> With delayed acks turned off,
> the acknowledgement may be sent in its own packet, before the remote service
> has a chance to echo the data it just received.
> This same concept also
> applies to any interactive protocol (e.g. SMTP, WWW, POP3), and can cut the
> number of tiny packets flowing across the network in half.
> The
> .Fx
> delayed ACK implementation also follows the TCP protocol rule that
539c548,549
< timeout has not yet passed. Normally the worst a delayed ack can do is
---
> timeout has not yet passed.
> Normally the worst a delayed ACK can do is
541c551,552
< of a slow-start TCP connection. While we aren't sure we believe that
---
> of a slow-start TCP connection.
> While we are not sure we believe that
543c554,556
< turning off delayed acks may be refering to the slow-start issue. In FreeBSD
---
> turning off delayed acks may be refering to the slow-start issue.
> In
> .Fx ,
547c560
< sysctl rather then disable delayed acks.
---
> sysctl rather than disable delayed acks.
554c567,568
< amount required to maintain optimum throughput. This feature is useful
---
> amount required to maintain optimum throughput.
> This feature is useful
557,558c571,572
< also using window scaling or have configured a large send window. If
< you enable this option you should also be sure to set
---
> also using window scaling or have configured a large send window.
> If you enable this option, you should also be sure to set
562c576,577
< to at least 6144 may be beneficial. Note, however, that setting high
---
> to at least 6144 may be beneficial.
> Note however, that setting high
566c581,582
< up in the local host's interface queue. With fewer packets queued up,
---
> up in the local host's interface queue.
> With fewer packets queued up,
568,569c584,587
< to operate with lower round trip times. However, note that this feature
< only effects data transmission (uploading / server-side). It does not
---
> to operate with lower round trip times.
> However, note that this feature
> only effects data transmission (uploading / server-side).
> It does not
575,576c593,599
< sockets. There are three ranges: A low range, a default range, and a
< high range, selectable via an IP_PORTRANGE setsockopt() call. Most
---
> sockets.
> There are three ranges: a low range, a default range, and a
> high range, selectable via the
> .Dv IP_PORTRANGE
> .Xr setsockopt 2
> call.
> Most
581,588c604,615
< which defaults to 1024 and 5000 respectively. Bound port ranges are
< used for outgoing connections and it is possible to run the system out
< of ports under certain circumstances. This most commonly occurs when you are
< running a heavily loaded web proxy. The port range is not an issue
< when running serves which handle mainly incoming connections such as a
< normal web server, or has a limited number of outgoing connections such
< as a mail relay. For situations where you may run yourself out of
< ports we recommend increasing
---
> which default to 1024 and 5000, respectively.
> Bound port ranges are
> used for outgoing connections, and it is possible to run the system out
> of ports under certain circumstances.
> This most commonly occurs when you are
> running a heavily loaded web proxy.
> The port range is not an issue
> when running serves which handle mainly incoming connections, such as a
> normal web server, or has a limited number of outgoing connections, such
> as a mail relay.
> For situations where you may run yourself out of
> ports, we recommend increasing
590,591c617,620
< modestly. A value of 10000 or 20000 or 30000 may be reasonable. You should
< also consider firewall effects when changing the port range. Some firewalls
---
> modestly.
> A value of 10000 or 20000 or 30000 may be reasonable.
> You should also consider firewall effects when changing the port range.
> Some firewalls
593c622,623
< to use higher ranges of ports for outgoing connections. For this reason
---
> to use higher ranges of ports for outgoing connections.
> For this reason,
641c671
< rather then later, eating more swap and disk bandwidth.
---
> rather than later, eating more swap and disk bandwidth.
858c888
< than 10BaseT, or use 1000BaseT rather then 100BaseT, depending on your needs.
---
> than 10BaseT, or use 1000BaseT rather than 100BaseT, depending on your needs.