0001203: Apache in worker mode instead of prefork - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001203

PacketFence

performance

public

2011-03-25 17:53

2011-10-25 09:03

Reporter

obilodeau

Assigned To

Priority

normal

Severity

minor

Reproducibility

N/A

Status

closed

Resolution

won't fix

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0001203: Apache in worker mode instead of prefork

Description

After looking more closely at what our default apache configuration file is doing, I realize that we can improve things.

We are running apache in prefork mode where one process handles one request at a time (no threading). We should see if our code works fine in the worker mode. We could serve a lot more requests with the same amount of RAM consumed if it does work.

On CentOS, the /usr/sbin/httpd.worker binary exists, I'm pretty sure that trying it and validating that the captive portal, the web admin and the Web Services back-end all work would be a good start.

Tags

No tags attached.

fixed in git revision

fixed in mtn revision

Attached Files

Relationships

Notes
(0002002) fgaudreault (viewer) 2011-03-25 21:39	You are aware that PHP recommends the usage of Apache Prefork? (Talking about the admin UI) I don't know if it's still the case, but it was writen in their manual for a while. If you want to use worker MPM, you'll need to compile PHP with Zend Thread Safety. CentOS doesn't compile it in their package. So we will need to either maintain a PHP version, or use another external repo. I don't want to be a pain, but RAM is so cheap these days...

(0002005) obilodeau (reporter) 2011-04-04 17:18	If this is the case then it's uninteresting for now.

Issue History
Date Modified	Username	Field	Change
2011-03-25 17:53	obilodeau	New Issue
2011-03-25 21:39	fgaudreault	Note Added: 0002002
2011-04-04 17:18	obilodeau	Note Added: 0002005
2011-04-04 17:18	obilodeau	Status	new => closed
2011-04-04 17:18	obilodeau	Resolution	open => won't fix
2011-10-25 09:03	obilodeau	Target Version	+1 =>