Project

General

Profile

Feature #1162

Adaptive spawning with min-procs=>0

Added by Anonymous over 10 years ago. Updated 5 months ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
mod_fastcgi
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Missing in 1.5.x:

Description

I understand that adaptive spawning is out of action for a while.

I gather it is designed so that at least one process is started and that a check is done periodically (one a second?) and additional processes are spawned if there is an overload.

Maybe this is the plan anyway. It would be great that if min-procs could be set to zero . In this case no processes are started until a request comes in which needs the particular fastcgi. If the fastcgi is not used for a while the number of processes can die back to 0.

Thanks, Richard Collins

-- richard

Associated revisions

Revision d66cbe95 (diff)
Added by gstrauss 5 months ago

[core] adaptive spawning for socket backend procs (fixes #1162)

experimental

enable adaptive spawning for socket backend processes

new feature will allow "min-procs" => "0" and will spawn a backend
upon receipt of a request, if no backends are currently running.
This may be useful on resource-limited systems where there is a
seldom-used resource-intensive backend, such as home router
configuration web pages. The first request may be slower as the
backend is starting up, but then subsequent requests within
"idle-timeout" will hit the (temporarily) persistent backend for
faster responses.

x-ref:
"Adaptive spawning with min-procs=>0"
https://redmine.lighttpd.net/issues/1162

History

#1

Updated by Anonymous over 10 years ago

I second that emotion--er, motion. It would be very nice to have at least this much adaptive spawning. Theoretically easier than full adaptive spawning, I should think. Of course, I've never even looked at lighty's code...

#2

Updated by gstrauss over 1 year ago

  • Assignee deleted (jan)
#3

Updated by gstrauss over 1 year ago

  • Target version deleted (1.5.0)
#4

Updated by gstrauss 5 months ago

  • Description updated (diff)
  • Status changed from New to Patch Pending
  • Target version set to 1.4.46
#5

Updated by gstrauss 5 months ago

  • Status changed from Patch Pending to Fixed
  • % Done changed from 0 to 100

Also available in: Atom