Let me rephrase my previous post.
One proxy worker is created for each ProxyPass directive or balancer member. A connection pool is associated with each worker. One single remote server is associated with each connection pool, and thus with each worker. This allows mod_proxy to establish persistent connections to backend servers that can be used across requests from different clients.
When using mod_rewrite for proxying (RewriteRule ... [P]), the backend connections are always created on the fly for each client request and do not benefit from the use of pooled (persistent) connections.
I am wondering whether it would be possible to enhance the implementation of mod_proxy so that workers and associated connection pools can be allocated whenever a new backend server is detected through the arrival of a request for which there is no worker.
In ap_proxy_pre_request() (modules/proxy/proxy_util.c: line 1395), if no worker is found, a default worker is returned. Instead a new worker could be created for scheme://address/
modules/proxy/proxy_util.c: line 1395 (current implementation in 2.2.4)
else if (r->proxyreq == PROXYREQ_REVERSE) {
if (conf->reverse) {
ap_log_rerror(APLOG_MARK, APLOG_DEBUG, 0, r,
"proxy: *: found reverse proxy worker for %s",
*url);
*balancer = NULL;
*worker = conf->reverse;
access_status = OK;
}
-ascs
-----Message d'origine-----
De : Axel-Stéphane SMORGRAV
Envoyé : mercredi 29 août 2007 19:18
À : users@xxxxxxxxxxxxxxxx
Objet : Apache 2.2.x mod_rewrite and mod_proxy and pooled connections
Hello folks,
I have been doing some testing with Apache 2.2.4 recently, and one of the things I am particularly interested in is the pooling of backend connections of mod_proxy's as this makes it possible to maintain persistent connections to backend systems across requests from different clients no matter whether the client connections are persistent or not.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|