Hi Folks. I've got a question regarding Thread::Pool. Basicaly, I'll be migrating a rather large user base over one weekend. I've so far got everything sorted out so that I can parse out all the data into flat text files, and can then start doing the migration.
So, my next worry then is to ensure every user actuallt gets migrated, and within as short a timespan as possible, of course. Now, for this I figured I'd use threading, and a pool of threads. Also means I'm running Perl 5.8.1 on Linux.. ;) So, my question then, if I hit the maxjobs limit, the doc's just say that <quote> The maxjobs method can be called to set the maximum number of jobs that may be on the belt before job submission will be halted. </quote> Would that then mean any further jobs that may want to end up in the pool may get lost, or will they sit there and wait until they can be submitted? A slight difference, which the doc's doesn't quite mention, and which may have a potentially large impact. So, anybody present which would have had experience with this? Just want to know if I need to change my approach or not.. Cheers! //Anders// -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
