Mercurial > hg > nginx-site

comparison xml/en/docs/freebsd_tuning.xml @ 271:4c6d2c614d2c

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Cleaned up XML tag mess: - all of <parameter> and <code>, and some of <dirname>, <value>, and <command> were replaced by <literal>; - the rest of <dirname> were replaced by links; - <argument> were replaced by <value>; - <value> is now rendered in HTML in italic; - <literal> and <path> can now contain <value>. Cleaned up terminology mess: - directives take "parameters".
author Ruslan Ermilov <ru@nginx.com>
date Fri, 23 Dec 2011 17:29:59 +0000
parents 682163f2b298
children be54c443235a
comparison
equal deleted inserted replaced
270:945d7299c26c 271:4c6d2c614d2c
98 98
99 <para> 99 <para>
100 When a client sends a data, the data first is received by the kernel 100 When a client sends a data, the data first is received by the kernel
101 which places the data in the socket receiving buffer. 101 which places the data in the socket receiving buffer.
102 Then an application such as the web server 102 Then an application such as the web server
103 may call <code>recv()</code> or <code>read()</code> system calls 103 may call <c-func>recv</c-func> or <c-func>read</c-func> system calls
104 to get the data from the buffer. 104 to get the data from the buffer.
105 When the application wants to send a data, it calls 105 When the application wants to send a data, it calls
106 <code>send()</code> or <code>write()</code> 106 <c-func>send</c-func> or <c-func>write</c-func>
107 system calls to place the data in the socket sending buffer. 107 system calls to place the data in the socket sending buffer.
108 Then the kernel manages to send the data from the buffer to the client. 108 Then the kernel manages to send the data from the buffer to the client.
109 In modern FreeBSD versions the default sizes of the socket receiving 109 In modern FreeBSD versions the default sizes of the socket receiving
110 and sending buffers are respectively 64K and 32K. 110 and sending buffers are respectively 64K and 32K.
111 You may change them on the fly using the sysctls 111 You may change them on the fly using the sysctls
237 and memory usage by using the cached file pages. 237 and memory usage by using the cached file pages.
238 </para> 238 </para>
239 239
240 <para> 240 <para>
241 And again, the amd64 sendfile implementation is the best: 241 And again, the amd64 sendfile implementation is the best:
242 the zeros in the <nobr>“<code>netstat -m</code>”</nobr> output 242 the zeros in the <nobr>“<literal>netstat -m</literal>”</nobr> output
243 <programlisting> 243 <programlisting>
244 ... 244 ...
245 <b>0/0/0</b> sfbufs in use (current/peak/max) 245 <b>0/0/0</b> sfbufs in use (current/peak/max)
246 ... 246 ...
247 </programlisting> 247 </programlisting>