On slow connections (like mine) the first request to python runserver.py serve takes
e
t
e
r
n
i
t
y
.
It's because the talks archive repo is cloning and basically everything is building. Maybe this could be happening only before the first request to the relevant routes? 🤔 The same could be true for all other requests doing significant computation.
On slow connections (like mine) the first request to
python runserver.py servetakese
t
e
r
n
i
t
y
.
It's because the talks archive repo is cloning and basically everything is building. Maybe this could be happening only before the first request to the relevant routes? 🤔 The same could be true for all other requests doing significant computation.