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 yanirh
Recipients paul.moore, steve.dower, tim.golden, yanirh, zach.ware
Date 2018-03-28.14:56:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1522248989.15.0.467229070634.issue33171@psf.upfronthosting.co.za>
In-reply-to
Content
I'm using either multiprocessing package or concurrent.futures for some embarrassingly parallel application.

I performed a simple test: basically making n_jobs calls for a simple function - 'sum(list(range(n)))', with n large enough so that the operation is a few seconds long - where n_jobs > n_logical_cores.

Tried it on two platforms:

first platform:
server with X4 Intel Xeon E5-4620 (8 physical, 16 logical), running 
a 64bit Windows Server 2012 R2 Standard.

***

second platform:
server with X2 Intel Xeon Gold 6138 (20 physical, 40 logical), running a 64bit Windows Server 2016 Standard.

***

first platform reaches 100% utilization.
second platform reaches 25% utilization.
History
Date User Action Args
2018-03-28 14:56:29yanirhsetrecipients: + yanirh, paul.moore, tim.golden, zach.ware, steve.dower
2018-03-28 14:56:29yanirhsetmessageid: <1522248989.15.0.467229070634.issue33171@psf.upfronthosting.co.za>
2018-03-28 14:56:29yanirhlinkissue33171 messages
2018-03-28 14:56:29yanirhcreate