Setting kill_thread_limit in paster's config ini file
Hi guys, I've been trying to set some of paster's threadpool options, but am failing miserably. The main one I want to to change is threadpool_kill_thread_limit (http://pythonpaste.org/modules/ httpserver.html#module-paste.httpserver) What do I need to put in the config to get this to work. I've tried just sticking threadpool_kill_thread_limit = 20 into [server:main] and [app:main] but neither has any effect. Any ideas on how to get this working? Thanks, Shayan Raghavjee -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: Setting kill_thread_limit in paster's config ini file
On Thu, May 6, 2010 at 11:22 PM, Shayan doch...@gmail.com wrote: Hi guys, I've been trying to set some of paster's threadpool options, but am failing miserably. The main one I want to to change is threadpool_kill_thread_limit (http://pythonpaste.org/modules/ httpserver.html#module-paste.httpserver) What do I need to put in the config to get this to work. I've tried just sticking threadpool_kill_thread_limit = 20 into [server:main] and [app:main] but neither has any effect. Any ideas on how to get this working? It's a bit difficult to figure out the variable names because they're not directly documented. Maybe 'kill_thread_limit' or '[threadpool-]kill-thread-limit'? You can also ask on the Paste list. If you get a definitive answer, please let us know. -- Mike Orr sluggos...@gmail.com -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: application deployment question about nginx and pylons
On Wed, Apr 28, 2010 at 5:02 PM, cd34 mcd...@gmail.com wrote: On Apr 27, 10:00 pm, Terry Schmitt tschm...@schmittworks.com wrote: Like Weixi Yen, my preference is the simplicity of using reverse proxy with Nginx. I've used this in the past for Java based apps. It's fast, easy to configure and I will probably use that as my first choice as I venture into the Python world. If you're looking for performance, I believe using a wsgi gateway will outperform proxypass - paster. While paster is great for development, at least in simple benchmarking I was never able to get it to go reliably beyond a few hundred concurrent connections. The CherryPy server also works with Pylons and is supposed to have better performance than PasteHTTPServer. There should be an INI configuration in the Pylons wiki or list archive. -- Mike Orr sluggos...@gmail.com -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
formatted_new_article, formatted_edit_article, ...
Hi list,
Every time I create a controller, the generated test contains multiple
url(formatted_*, ...), e.g.:
def test_edit_as_xml(self):
response = self.app.get(url('formatted_edit_article', id=1,
format='xml'), headers=self.headers)
I was wondering what this was supposed to be used for. Request article
edition from an XML document? I don't have to implement this, but I
was just curious of the purpose of such test and how I should
interpret it.
--
Alex
twitter.com/alexconrad
--
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-disc...@googlegroups.com.
To unsubscribe from this group, send email to
pylons-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
Re: application deployment question about nginx and pylons
On May 7, 12:53 pm, Mike Orr sluggos...@gmail.com wrote: The CherryPy server also works with Pylons and is supposed to have better performance than PasteHTTPServer. There should be an INI configuration in the Pylons wiki or list archive. I'm reasonably happy with apache2-mpm-worker/mod_wsgi or nginx/uwsgi. I am currently using varnish in conjunction with both for another project, but, what are the relative benefits of using one of the few dozen deployment situations listed? nginx - proxypass (paster, cherrypy) nginx - fastcgi nginx - wsgi (uwsgi, mod_passenger, mod_wsgi (their somewhat broken implementation that has had some recent work done)) apache - mod_proxy (paster, cherrypy) apache - fastcgi apache - mod_python apache - mod_wsgi (embedded, daemon) apache - mod_passenger lighttpd - fastcgi lighttpd - proxy (paster, cherrypy) This doesn't include cherokee with its native wsgi support and half a dozen other implementations. As Graham Dumpleton indicates, Apache is very capable in a lot of situations and I've had no problem running apache for clients handling 300m pageviews a month on 4 machines. The reason I've recently moved to nginx is that I can now handle the static media on nginx, utilize ncache (now that it is built in), utilize uwsgi which delivers great performance and I eliminate having to maintain nginx - proxypass - apache - mod_wsgi - pylons. My stack now looks like nginx - uwsgi - pylons. Simplicity should lead to better reliability or so one would hope. -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: formatted_new_article, formatted_edit_article, ...
On Fri, May 7, 2010 at 4:17 PM, Alexandre Conrad
alexandre.con...@gmail.com wrote:
Hi list,
Every time I create a controller, the generated test contains multiple
url(formatted_*, ...), e.g.:
def test_edit_as_xml(self):
response = self.app.get(url('formatted_edit_article', id=1,
format='xml'), headers=self.headers)
I was wondering what this was supposed to be used for. Request article
edition from an XML document? I don't have to implement this, but I
was just curious of the purpose of such test and how I should
interpret it.
The routes created by map.resource include a 'formatted_*' route
alongside each regular route. The formatted routes have a '.FORMAT'
suffix at the end of the URL; e.g., /articles/1234.xml, which you can
access via the 'format' routing variable. This allows you to return
the data in an alternate format. Of course, your action would have to
support those formats or abort(404) if it doesn't. I don't know what
editing in XML format would mean, or whether multi-formats makes sense
for any action besides view. But if you had a web service that could
accept either JSON or XML or other formats, it might work for that.
--
Mike Orr sluggos...@gmail.com
--
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-disc...@googlegroups.com.
To unsubscribe from this group, send email to
pylons-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
