[Django] #30112: python manage.py runserver very long response time
Django
-----------------------------------------+------------------------
Reporter: smudgerPH | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 2.1
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 |
-----------------------------------------+------------------------
When I run 'python manage.py runserver' it takes at least 20 minutes
before performing any system checks, it then takes a further 10 minutes to
do the system checks. If there is an error with the code or database then
it still takes this long before saying anything.
I have the latest version of pip, Python and Django. I've looked on the
task manage and the command prompt is using 0.1% of the CPU during this
time. It also takes this long for me to run 'python manage.py migrate'. I
seem to be the only one working on the project that has this problem.
Once it does start running the server, if I edit any pages and try to
reload them then the server becomes unreachable but gives the impression
in the command prompt that it is still running. I have to restart the
server to see any changes.
I'm running windows 10 on a personal laptop with an 8th gen i7 processor.
While running this command I am doing nothing else and the total usage of
the CPU rarely goes above 10% so I can't see any reason why it takes so
long.
--
Ticket URL: <https://code.djangoproject.com/ticket/30112>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: smudgerPH | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 2.1
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
Comment:
You need to give us some way to reproduce the problem (and ideally,
confirm that Django is at fault).
--
Ticket URL: <https://code.djangoproject.com/ticket/30112#comment:1>