Thanks to visit codestin.com
Credit goes to github.com

Skip to content

FPM: Change last_idle_child lookup to fix idle time computation #4104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

mpdude
Copy link

@mpdude mpdude commented May 3, 2019

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 this last_idle_child to decide if it should be terminated.

Thus, I think we need to determine the last_idle_childby looking at the time of the last request served, not the startup time.

Currently, the "last_idle_child" is determined by looking at the
starting time, that is, it is the child that has been around for
the longest time.

A few lines later, for pm = ondemand the idle time is computed for
this last_idle_child to decide if it has been idle too long and
should be terminated.

To make this calculation correct, we need to find the "last_idle_child"
by looking at the time of the last request served, not the startup
time.
@nikic nikic requested a review from bukka May 7, 2019 08:23
@krakjoe
Copy link
Member

krakjoe commented May 25, 2019

@bukka can you take a look at this one please ?

@bukka
Copy link
Member

bukka commented May 26, 2019

I think this would make sense if we had FIFO selection as discussed in #4101 . However I'm not sure if it makes much difference for the round robin selection (accept).

@mpdude Have you seen any improvements with this patch when testing?

@cmb69
Copy link
Member

cmb69 commented Jun 12, 2019

@mpdude, any news?

@mpdude
Copy link
Author

mpdude commented Jun 13, 2019

No, I haven’t done any performance research. I am not even sure how I would do this and what to look out for 🤔

I found this while studying the code and wanted to bring it to the attention of someone who knows better than me 🤷🏻‍♂️

@ramsey
Copy link
Member

ramsey commented May 27, 2022

@mpdude Are you interested in pursuing this PR? If not, please feel free to close it. Thanks!

@github-actions
Copy link

There has not been any recent activity in this PR. It will automatically be closed in 7 days if no further action is taken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants