This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skip.montanaro
Recipients skip.montanaro
Date 2008-10-11.12:36:11
SpamBayes Score 1.7326033e-07
Marked as misclassified No
Message-id <1223728573.75.0.409480636463.issue4106@psf.upfronthosting.co.za>
In-reply-to
Content
Final comment before I see some feedback from the experts.

I have this code in the worker function's loop:

    # quick pause to allow other stuff to happen a bit randomly
    t = 0.1 * random.random()
    time.sleep(t)

If I eliminate the sleep altogether pretty much all hell breaks loose.
As I reduce the sleep time it gets noisier and noisier.  I switched to
a fixed sleep time and reduced it as far as

    time.sleep(0.00015625)

At that point it was complaining about killing worker processes on
many of the runs, maybe 1 out of every 5 or 10 runs.

I suppose the moral of the story is to not use multiprocessing except
when you have long-running tasks.
History
Date User Action Args
2008-10-11 12:36:13skip.montanarosetrecipients: + skip.montanaro
2008-10-11 12:36:13skip.montanarosetmessageid: <1223728573.75.0.409480636463.issue4106@psf.upfronthosting.co.za>
2008-10-11 12:36:12skip.montanarolinkissue4106 messages
2008-10-11 12:36:12skip.montanarocreate