r4120 - branches/sky/wrw_context_gzip/varnish-cache/bin/varnishd
sky at projects.linpro.no
sky at projects.linpro.no
Wed Jun 17 16:30:42 CEST 2009
Author: sky
Date: 2009-06-17 16:30:42 +0200 (Wed, 17 Jun 2009)
New Revision: 4120
Modified:
branches/sky/wrw_context_gzip/varnish-cache/bin/varnishd/cache_wrw.c
Log:
comment does not belong here
Modified: branches/sky/wrw_context_gzip/varnish-cache/bin/varnishd/cache_wrw.c
===================================================================
--- branches/sky/wrw_context_gzip/varnish-cache/bin/varnishd/cache_wrw.c 2009-06-17 14:16:59 UTC (rev 4119)
+++ branches/sky/wrw_context_gzip/varnish-cache/bin/varnishd/cache_wrw.c 2009-06-17 14:30:42 UTC (rev 4120)
@@ -26,18 +26,6 @@
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
- * We maintain a number of worker thread pools, to spread lock contention.
- *
- * Pools can be added on the fly, as a means to mitigate lock contention,
- * but can only be removed again by a restart. (XXX: we could fix that)
- *
- * Two threads herd the pools, one eliminates idle threads and aggregates
- * statistics for all the pools, the other thread creates new threads
- * on demand, subject to various numerical constraints.
- *
- * The algorithm for when to create threads needs to be reactive enough
- * to handle startup spikes, but sufficiently attenuated to not cause
- * thread pileups. This remains subject for improvement.
*/
#include "config.h"
More information about the varnish-commit
mailing list