Aaron Swartz wrote: > Why wouldn't it? You're not creating any new threads, you're > not saving anything and calling it later... > Am I missing something?
No, I am, probably :) I have just been confused at Python threading since forever. So I thought web.py could be doing some hardcore magic I'm not aware of. I took some time today to read about the GIL. I'm using web.py with "multiplexed" Flup. I basically have 4 instances of web.py running the Flup FCGI server that is returned by wsgifunc(). They're all behind nginx, which load-balances requests. This multiplxed Flup server, from what I understand, runs several threads but since it's Python, they all run in the same processor, right? Does it perform nicely from your experience? It seems to, but I was just wondering if I should be concerned at all about this. One more question: to run these web.py instances, I void sys.std(in| out|err) using a snippet I found here (using a "NullDevice" class) and just put them in the background appending "&" to the command line. Is this a good enough way to do this? Should I be looking at more sophisticated approaches? Thanks in advance for any clarification! --Jonas Galvez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
