the original throttling in the gwtoolset form allowed a user to limit the number of threads carried out per job runner run, but i think that has changed. someone on the previous multimedia team might know if the throttle field still has any impact or not. if it does, try setting it to 1.
still, this issue brings up a few features that would be ideal. a method that allows the originator of the batch job or an admin: * the ability to cancel the batch job * the ability to slow down the batch job * the ability to monitor the batch job with kind regards, dan On Wed, Jun 3, 2015 at 11:51 AM, Brian Wolff <[email protected]> wrote: >>[..] or indeed provide a >> playpen where the nuts and bolts of internet transaction problems are >> handled by off-the-shelf secondary playpen modules. Okay, it's >> fantasy, but you never know. ;-) >> >> Fae > > I don't think I understand what you mean by that. Are you hoping that > gwtoolset will be allowed to load things from tool labs in the future? > > -- > bawolff > > _______________________________________________ > Glamtools mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/glamtools _______________________________________________ Glamtools mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/glamtools
