FPM: Change last_idle_child lookup to fix idle time computation #4104
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the
last_idle_child
is determined by looking at the start time. That is, it is the child that has been around for the longest period of time.A few lines later, for
pm = ondemand
the idle time is computed for thislast_idle_child
to decide if it should be terminated.Thus, I think we need to determine the
last_idle_child
by looking at the time of the last request served, not the startup time.