Project

General

Profile

Bug #1796

Be more fair on fastcgi children request handling of mod_fastcgi

Added by qhy about 11 years ago. Updated almost 11 years ago.

Status:
Missing Feedback
Priority:
Low
Assignee:
-
Category:
mod_fastcgi
Target version:
-
Start date:
2008-10-14
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

Current mod_fastcgi's children selection algorithm makes small number of fastcgi children servers most of request. Below is report from mod_status

-------
fastcgi.active-requests: 1
fastcgi.backend.localhost.0.connected: 5
fastcgi.backend.localhost.0.died: 0
fastcgi.backend.localhost.0.disabled: 0
fastcgi.backend.localhost.0.load: 0
fastcgi.backend.localhost.0.overloaded: 0
fastcgi.backend.localhost.1.connected: 4
fastcgi.backend.localhost.1.died: 0
fastcgi.backend.localhost.1.disabled: 0
fastcgi.backend.localhost.1.load: 0
fastcgi.backend.localhost.1.overloaded: 0
..............
fastcgi.backend.localhost.63.connected: 45
fastcgi.backend.localhost.63.died: 0
fastcgi.backend.localhost.63.disabled: 0
fastcgi.backend.localhost.63.load: 1
fastcgi.backend.localhost.63.overloaded: 0

---------
fastcgi.backend.localhost.63 servers about ten times request of fastcgi.backend.localhost.0

patch to remedy the problem is attached

mod_fastcgi.patch (659 Bytes) mod_fastcgi.patch patch to lighttpd 1.4.20 qhy, 2008-10-14 15:27

History

#1

Updated by Olaf-van-der-Spek about 11 years ago

qhy wrote:

Current mod_fastcgi's children selection algorithm makes small number of fastcgi children servers most of request. Below is report from mod_status

What is the problem? And why?

#2

Updated by stbuehler about 11 years ago

  • Status changed from New to Need Feedback
  • Priority changed from High to Low
  1. I don't see a problem if one backend gets more requests than another as long as the load is balanced.
  2. Assume you have two backends, but only one is needed. If you always take the first, the second one can be swapped to disk. If you enforce your "fair" scheduling, you need both in memory (and there may be other cache optimizations you kill).

To sum it up: I don't think changing the default behaviour is a good idea in any case; the only thing we could discuss is to have an option for it.

Apart from that: you neither explained why this is a bug nor why it should be "high" priority - and i really don't like that.

#3

Updated by stbuehler almost 11 years ago

  • Status changed from Need Feedback to Missing Feedback

Also available in: Atom