I'll have probably six to a dozen scripts once the website is complete, but I can easily see that doubling by the end of next year. Though there will only be one or two scripts which will get extremely large amounts of traffic (my site is a live sports fantasy stat viewer) since they refresh every 30 seconds with new data. Meaning if five people are using my site for viewing one game live, there will be roughly 1500 page views. The page consists of reading a text file of roughly a megabyte, extracting the match data and then the usual formatting (with a few dozen MySQL queries). Obviously this script and the one which collects the data are going to put the most load on the server, so maybe they should have their own separate interpreter while other scripts rely on a couple? The other scripts aren't load intensive at all and deal with only a couple MySQL queries.
Now if all of a sudden 6 or 7 people start using my live stat viewer for each game ( ~ 15000 page views and ~ 1 million MySQL queries over three days), I'll probably need to upgrade my server altogether unless I'm underestimating the power of modwsgi and 360mb of VPS RAM. But let's worry about what I can control at the moment. I'm assuming this page ( http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives ) deals with sub interpreters? Not understanding too much of it... Is it the 'WSGIRestrictProcess' section? Is there anyway to see if it's working once I implement it? -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en.
