#30372: Django (moderately) High CPU usage at Idle
-----------------------------------------------+------------------------
               Reporter:  Benjamin Schollnick  |          Owner:  nobody
                   Type:  Bug                  |         Status:  new
              Component:  Core (Other)         |        Version:  2.2
               Severity:  Normal               |       Keywords:
           Triage Stage:  Unreviewed           |      Has patch:  0
    Needs documentation:  0                    |    Needs tests:  0
Patch needs improvement:  0                    |  Easy pickings:  0
                  UI/UX:  0                    |
-----------------------------------------------+------------------------
 I just noticed that Django at idle, using the Dev server, was taking up on
 average 10-15% of my CPU.

 That seems high, and it appears to be the reload system, using "manage.py
 runserver --noreload" dropped it to 0%.

 This is consistent, and has occurred over multiple runs of the django app.

 I have not added any additional watched folders, and the app was at idle,
 awaiting connection.

 My research leads me to believe there were changes to formalize the Django
 watched folder mechanisms into a formal API.
 It's unclear if this is a bug, or just need significant further
 optimization.

 This is under MOSX 10.14.4, 2.9 Ghz i5, 8 Gb ram.

 Python 3.7.2

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30372>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/054.17d6039d085cf1084536a882dc9093a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to