On Thu, Sep 27, 2012 at 1:36 AM, Federico Leva (Nemo) <[email protected]> wrote: >> In general in Labs we don't have a large need for a queuing system >> right now. > > Of course, because nobody is using it right now. I suppose Toolserver didn't > need it when it had only a few users consuming its resources. >
I should know better than to feed a troll, but Labs is relatively heavily used. At this moment there are 233 virtual machines running across 125 projects. It's actively used by quite a number of bots (which have already moved from Toolserver). It's being used by the following teams; * Analytics * Editor-engagement * Visual editor * Global education * QA * Mobile * Pediapress * Localization * Wikidata * Operations * Fundraising * Core services Many of those teams host multiple active projects. Additionally, we have a number of volunteer driven projects. Here's a few choice ones: * Bots * Deployment-prep * Maps (for OpenStreetMaps) * Wikistats * Wikitrust * Signwriting * Phabricator * Metavidwiki * Huggle * Glam * Wiki loves monuments * Blamemaps * Counter vandalism network It was used extensively during Google summer of code by the students and mentors. It's also used very heavily during hackathons; most projects demo at the end with Labs. These projects aren't in great need of a queue because they don't fight against each other for shared resources. When bots and tools are added that need to do expensive, long-running queries against a set of common databases we'll likely need some form of queuing system, but it hasn't been a high priority since we haven't been working on Toolserver like features. - Ryan _______________________________________________ Toolserver-l mailing list ([email protected]) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
