Difference between revisions of "Server Architecture"
From LVSKB
(→Software Software) |
|||
| Line 24: | Line 24: | ||
Squid uses the single-process event-driven architecture, because the main process of squid handles all kind of network connections, despite that different processes can handle disk I/O under the diskd configuration. | Squid uses the single-process event-driven architecture, because the main process of squid handles all kind of network connections, despite that different processes can handle disk I/O under the diskd configuration. | ||
| + | |||
| + | === Varnish === | ||
| + | |||
| + | [[Varnish]] uses the single-process event-driven architecture, because the main process of Varnish uses poll to process events. | ||
== References == | == References == | ||
| Line 29: | Line 33: | ||
* http://nginx.net/ | * http://nginx.net/ | ||
* http://lighttpd.net/ | * http://lighttpd.net/ | ||
| + | * http://varnish.projects.linpro.no/ | ||
Revision as of 13:31, 27 June 2007
Server Architecture
Multiple-Process Architecture
Multiple-Thread Architecture
Single-Process Event-Driven Architecture
Multiple-Process Event-Driven Architecture
Multiple-Thread Event-Driven Architecture
Software Software
nginx
Nginx supports both the single-process event-driven architecture and the multiple-process event-driven architecture.
lighttpd
Lighttpd uses the single-process event-driven architecture.
squid
Squid uses the single-process event-driven architecture, because the main process of squid handles all kind of network connections, despite that different processes can handle disk I/O under the diskd configuration.
Varnish
Varnish uses the single-process event-driven architecture, because the main process of Varnish uses poll to process events.
