Okay, sorry, still another question. Each code.py, when run as fastcgi, seems to start 5 threads. I wonder where this number comes from, in the source of flup I have noticed that 5 threads is the default number. Is it meaningful to increase this number? If so, how to do it from my scripts? Does flup handle the tearing down of threads by itself, or does it get signals from the fastcgi mod? Thanks for any answers, greetings, Dragan
Am 16.12.2011 09:26, schrieb Dragan Espenschied: > Sorry people, > I figured it out. Using another task viewer I could see all the nice processes > that were in fact already running. So it works out of the box very nicely. > Till my next stupid question, > Dragan :) > > Am 15.12.2011 13:34, schrieb Dragan Espenschied: >> Hello, >> >> I am running three different webpy scripts via apache's fastcgi. I followed >> the >> instructions and it works great! >> >> But I wonder why only three instances of python are running on my server, one >> for each script. I thought, fastcgi would run multiple instaces of the >> scripts? >> >> Is there something in webpy that prevents more instances from being run? >> >> Do I need to configure fastcgi differently? >> >> >> My server is totally bored, with a very low load, and still visitors have to >> wait for answers from the three scripts. My server could easil run each >> script >> ten times. >> >> Thanks for any hints. >> >> Best greetings, >> Dragan >> > -- http://noobz.cc/ http://digitalfolklore.org/ http://contemporary-home-computing.org/1tb/ -- You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to webpy@googlegroups.com. To unsubscribe from this group, send email to webpy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
