Why does every Python app on Apache need new processes whereas PHP apps don't?

Question

I use webfaction's shared hosting services for my python/php apps. There is one thing I don't understand.

Every time, I install a new PHP app, no new processes are created. But installing a new Python app creates at least 3 new processes on the server.

Why does each Python app require several processes whereas PHP apps don't?

EDIT: The python apps run with WSGI on Apache.

score 1 · Answer 1 · answered Oct 04 '10 at 16:31

1

You didn't tell us enough to answer the question. There are several ways to write python apps, among them: CGI (does inherently require a process per connection), FastCGI (a pool of reusable python processes, with controllable size, is created and services connections - maybe it is too big for you?) and WSGI (Apache creates python interpreters in its threads, like PHP does). Please tell us the way you run your python apps from Apache.

answered Oct 04 '10 at 16:31

AEP

432
2
4

Sorry, I didn't know that this was important. The python apps run with WSGI on Apache. – Mert Nuhoglu Oct 04 '10 at 18:16
Maybe you need a configuration directive like this: WSGIDaemonProcess default processes=2 threads=25 – AEP Oct 06 '10 at 05:01

score 0 · Answer 2 · answered Oct 04 '10 at 17:56

0

I suggest you reimplement your python web applications with wsgi support.

answered Oct 04 '10 at 17:56

RussellBallestrini

301
1
2
8

Why does every Python app on Apache need new processes whereas PHP apps don't?

2 Answers2