#30383: Performance issue with ThreadPoolExecutor/Multiprocessing
-------------------------------------+-------------------------------------
               Reporter:  shonejin   |          Owner:  nobody
                   Type:             |         Status:  new
  Uncategorized                      |
              Component:             |        Version:  2.2
  Uncategorized                      |       Keywords:  performance,
               Severity:  Normal     |  multiprocessing, pool
           Triage Stage:             |      Has patch:  0
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 When starting a background task that directly/indirectly use Python's
 ThreadPoolExecutor or Multiprocessing, I notice each pool worker can only
 utilize a small portion of CPU, leaving  major of the CPU free. However,
 if I execute the same code outside of Django, the CPU utilization goes up
 by 5 times and thus performance improves a lot. I also tried
 "subprocess.call()" in Django to call 'python EXTERNAL_CODE.py' to run the
 computing but the CPU utilization issue is still there.

 No documentations available explaining why this happens, any supplement
 info is helpful! Thanks!

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30383>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.62fb77afbf8fbf472c004be47ebd39d8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to