About Archive Tag Cloud Translations RSS

You are writing a comment about Overview of Single vs. Multi Server Architecture, here is a quick summary:

I've been thinking a bit more about all the various deployment options for Django, and more specifically how the variety of options can be a bit bewildering for those who haven't setup a server before. Here is a picture-assisted guide to the distinctions between single and multi server architectures.


You are responding to this comment written by Graham Dumpleton on February 16th 2009, 23:49.

The statement:

"""This is because each mod_python worker thread needs a Python interpreter associated with it, causing each worker thread to consume approximately 20 megs of ram."""

is incorrect, or misleading at best if I give you the benefit of the doubt and take it as you just badly wording what was meant.

Each mod_python worker thread does not need or use a distinct Python interpreter. Threads will operate in the single existing Python interpreter for a particular context. The default context for mod_python is the virtual host. Individual threads should not be consuming 20MB of ram. If you are seeing that, then it is something else.

I stopped reading at this point as don't have the time to respond right now in more depth, but will read article properly later and then respond further if need be.


Please be aware that comment forms go stale after one hour.





Comments may make use of LifeFlow MarkDown. Raw html will be escaped.


Quick Introduction to LifeFlow MarkDown Syntax

A highlighted code block:

@@ ruby
def a (b, c):
  b * c
end
@@

Other common languages work as well: scheme, python, java, html, etc.

Other markdown syntax:

 ### This is an h3 title
#### This is an h4 title
**this is bold**
*this is italics*

1. This is an
2. ordered list

* And an unordered
* list too

[this is a link](http://www.lethain.com/ "Lethain")