So again, for catscan2, which resources? Memory? DB connections? http connections? I can see how catscan2 might be heavy, but catfood is rather light-weight, and I really can't see how it could eat up http connections.
Is it possible that whatever caused PHP to melt down last time is really a PHP issue, processes running forever or something like that? These tools have been up for months, presumably got the same traffic (forwarded from toolserver) and didn't show any such issues. That the two of them should suddenly start killing the server seems somewhat suspicious to me. Cheers, Magnus On Tue, Oct 8, 2013 at 7:31 PM, Marc A. Pelletier <[email protected]> wrote: > Hey all, > > Due to those two tools' web interfaces growing to consume all resources > on the webservers and impacting the other tools, I've had to temporarily > disable them. > > I'll be looking in the short term to deploy tool-specific webservers for > the "heavy duty" tools, so that their usage cannot impact the majority > of the tools -- this way, when a tool becomes overwhelming it'll be > moved to a separate server where it can only overwhelm itself. > > With a bit of luck, I might be able to do this during the week. If you > need your tool back up in the meantime, you can remove the .htaccess I > added to your public_html but if you do so please look into some form of > rate limiting. > > -- Marc > > _______________________________________________ > Labs-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/labs-l > -- undefined
_______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
