httpd 2.4.23 中文文档time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more memory, but it wouldn't be the safest option for the sake of the server's stability and memory footprint. Background material The event model was made possible by the introduction of new APIs into the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The0 码力 | 2559 页 | 2.11 MB | 1 年前3- httpd 2.4.25 中文文档time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more memory, but it wouldn't be the safest option for the sake of the server's stability and memory footprint. Background material The event model was made possible by the introduction of new APIs into the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The0 码力 | 2573 页 | 2.12 MB | 1 年前3
- httpd 2.4.28 中文文档time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more memory, but it wouldn't be the safest option for the sake of the server's stability and memory footprint. Background material The event model was made possible by the introduction of new APIs into the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The0 码力 | 2659 页 | 3.10 MB | 1 年前3
- httpd 2.4.33 中文文档time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more memory, but it wouldn't be the safest option for the sake of the server's stability and memory footprint. Background material The event model was made possible by the introduction of new APIs into the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The0 码力 | 2692 页 | 3.12 MB | 1 年前3
Apache HTTP Server Documentation Version 2.4time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. • The EVENT MPM is threaded like the Worker MPM, but is designed to allow chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The always need more memory than HTTP/1.1 processing. There are three directives which steer the memory footprint of a HTTP/2 connection: H2MAXSESSIONSTREAMS, H2WINDOWSIZE and H2STREAMMAXMEMSIZE. H2MAXSESSIONSTREAMS0 码力 | 1125 页 | 4.15 MB | 1 年前3- Apache HTTP Server Documentation Version 2.4time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. • The EVENT MPM is threaded like the Worker MPM, but is designed to allow chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The always need more memory than HTTP/1.1 processing. There are three directives which steer the memory footprint of a HTTP/2 connection: H2MAXSESSIONSTREAMS, H2WINDOWSIZE and H2STREAMMAXMEMSIZE. H2MAXSESSIONSTREAMS0 码力 | 1111 页 | 4.11 MB | 1 年前3
- httpd 2.4.20 中文文档time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more memory, but it wouldn't be the safest option for the sake of the server's stability and memory footprint. Background material The event model was made possible by the introduction of new APIs into the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The0 码力 | 2533 页 | 2.09 MB | 1 年前3
- httpd 2.4.8.dev 中文文档time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The0 码力 | 2404 页 | 1.84 MB | 1 年前3
- httpd 2.4.9 中文文档time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The0 码力 | 2398 页 | 1.84 MB | 1 年前3
- httpd 2.4.16 中文文档time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The0 码力 | 2438 页 | 1.87 MB | 1 年前3
共 23 条
- 1
- 2
- 3