How to manage a 3000 Perl mechanize Scripts?

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

Hi Monks,

How can I manage a 3000 Perl mechanize Scripts? To schedule its running time, manage logs and other enhancements. Is there a software (like cron) for this. I plan to run the 3000 scripts daily in a server?

Thanks in advance.

Roberto Ricardo

Comment on How to manage a 3000 Perl mechanize Scripts?

Replies are listed 'Best First'.
Re: How to manage a 3000 Perl mechanize Scripts? by ww (Archbishop) on Jan 02, 2014 at 13:58 UTC
Insufficient information, even if you're agnostic as to the means of running your "3000 scripts." Is this even remotely a Perl question -- ie, are you looking for a way to control the mechanize scripts with an overarching Perl parent... or something else. What's your target OS? Does it have `cron` or a comparable scheduler? How long does each script take to run? Does that vary significantly from script to script? What provisions have you made (cf, next question) for a script that can't/doesn't complete its run? Is there any requirement that the scripts run sequentially? Are you abiding by any relevant ToS? These may help you reformulate your question: On asking for help and How do I post a question effectively?. Quis custodiet ipsos custodes. Juvenal, Satires	[reply] [d/l]
Re^2: How to manage a 3000 Perl mechanize Scripts? by Anonymous Monk on Jan 03, 2014 at 03:46 UTC
I believe this is a rehash of Hiya Monks!	[reply]
Re: How to manage a 3000 Perl mechanize Scripts? by roboticus (Chancellor) on Jan 02, 2014 at 13:58 UTC
If you want something like cron, why not use cron? Is there some constraint that you're not telling us? ...roboticus When your only tool is a hammer, all problems look like your thumb.	[reply]
Re^2: How to manage a 3000 Perl mechanize Scripts? by jae_63 (Beadle) on Jan 02, 2014 at 19:46 UTC
Hudson and Jenkins are next-generation versions of cron. We use Hudson at my new workplace, and all of us are pretty happy with it. It has many features beyond cron; among them are support for pulling updates from Git/Subversion, detecting run-failures, automatic emails to the culprits, etc.	[reply]
Re: How to manage a 3000 Perl mechanize Scripts? by atcroft (Abbot) on Jan 02, 2014 at 18:43 UTC
As a single piece, I don't know. I do know that with a few modules you could cobble together something to handle them that could be launched via cron. If you are concerned about load and do not need them all running simultaneously, then something like Parallel::ForkManager could enable you to run N jobs simultaneously, allowing you to launch the next job when a previous one had finished. It boils down to needing more information to know exactly what you are wanting. Hope that helps.	[reply]