Comments on: Benchmark followup: Google-code Edition http://jessenoller.com/2007/09/16/benchmark-followup-google-code-edition/ python, programming and other things Mon, 02 Jan 2012 09:21:00 +0000 hourly 1 By: Doug Napoleone http://jessenoller.com/2007/09/16/benchmark-followup-google-code-edition/comment-page-1/#comment-6200 Doug Napoleone Mon, 17 Sep 2007 16:46:34 +0000 http://jessenoller.com/2007/09/16/benchmark-followup-google-code-edition/#comment-6200 Quite off topic, but I would recommend 'If you give a Moose a Muffin' as well as the other books by that author. (Oh and the entire series from the author of 'Click Clack Moo'.) Quite off topic, but I would recommend ‘If you give a Moose a Muffin’ as well as the other books by that author. (Oh and the entire series from the author of ‘Click Clack Moo’.)

]]> By: jesse http://jessenoller.com/2007/09/16/benchmark-followup-google-code-edition/comment-page-1/#comment-6099 jesse Mon, 17 Sep 2007 00:47:51 +0000 http://jessenoller.com/2007/09/16/benchmark-followup-google-code-edition/#comment-6099 Thanks for the information - one of the key things that was brought up to me in private is to make sure that if "we" found "something" that was attractive, that we should make sure that projects like web.py/django/TG/etc could take advantage of it. As for: <blockquote> "Because of the way the web servers can distribute requests across multiple processes, one can very easily make use of multiple processors and cores with no change to applications." </blockquote> You're dead on - and I had forgotten that very valid point in this discussion. I've added your information and links to the wiki Thanks for the information — one of the key things that was brought up to me in private is to make sure that if “we” found “something” that was attractive, that we should make sure that projects like web.py/django/TG/etc could take advantage of it.

As for:

“Because of the way the web servers can distribute requests across multiple processes, one can very easily make use of multiple processors and cores with no change to applications.“

You’re dead on — and I had forgotten that very valid point in this discussion.

I’ve added your information and links to the wiki

]]> By: Graham Dumpleton http://jessenoller.com/2007/09/16/benchmark-followup-google-code-edition/comment-page-1/#comment-6098 Graham Dumpleton Mon, 17 Sep 2007 00:43:07 +0000 http://jessenoller.com/2007/09/16/benchmark-followup-google-code-edition/#comment-6098 Please also consider referencing the existing solutions for Python web frameworks that have been round for many years. In particular, multi process web servers such as Apache where Python can be embedded within the server processes using mod_python or mod_wsgi. Other possible solutions are daemon mode of mod_wsgi, mod_fastcgi, mod_fcgid and mod_scgi modules for Apache. These allow multiple daemon processes to be created and to some degree managed by Apache, and to which HTTP requests can be proxied for processing. Other web servers such as lighttpd and nginx also support fastcgi functionality. Because of the way the web servers can distribute requests across multiple processes, one can very easily make use of multiple processors and cores with no change to applications. For my original response to comments made by Guido in this Parallel Python discussion outlining these solutions see: http://blog.dscpl.com.au/2007/09/parallel-python-discussion-and-modwsgi.html An older blog entry: http://blog.dscpl.com.au/2007/07/web-hosting-landscape-and-modwsgi.html also describes why the Python GIL is not as big a deal in Python web applications hosted under Apache as some think it is. Please also consider referencing the existing solutions for Python web frameworks that have been round for many years. In particular, multi process web servers such as Apache where Python can be embedded within the server processes using mod_python or mod_wsgi. Other possible solutions are daemon mode of mod_wsgi, mod_fastcgi, mod_fcgid and mod_scgi modules for Apache. These allow multiple daemon processes to be created and to some degree managed by Apache, and to which HTTP requests can be proxied for processing. Other web servers such as lighttpd and nginx also support fastcgi functionality.

Because of the way the web servers can distribute requests across multiple processes, one can very easily make use of multiple processors and cores with no change to applications.

For my original response to comments made by Guido in this Parallel Python discussion outlining these solutions see:

http://blog.dscpl.com.au/2007/09/parallel-python-discussion-and-modwsgi.html

An older blog entry:

http://blog.dscpl.com.au/2007/07/web-hosting-landscape-and-modwsgi.html

also describes why the Python GIL is not as big a deal in Python web applications hosted under Apache as some think it is.

]]> By: jessenoller.com - Have GIL: Want Benchmarks. http://jessenoller.com/2007/09/16/benchmark-followup-google-code-edition/comment-page-1/#comment-6097 jessenoller.com - Have GIL: Want Benchmarks. Mon, 17 Sep 2007 00:40:44 +0000 http://jessenoller.com/2007/09/16/benchmark-followup-google-code-edition/#comment-6097 [...] A thing of Note: I've spawned an initial google code project to explore the alternatives/benchmarks. Read about it here. [...] […] A thing of Note: I’ve spawned an initial google code project to explore the alternatives/benchmarks. Read about it here. […]

]]>