Closed
Bug 1054257
Opened 10 years ago
Closed 4 years ago
VM performance impacts regeneration of Stylus files
Categories
(developer.mozilla.org Graveyard :: Performance, defect)
developer.mozilla.org Graveyard
Performance
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jezdez, Unassigned)
References
Details
See the original ticket: https://github.com/mozilla/kuma/issues/2519
Reporter | ||
Comment 1•8 years ago
|
||
:shobson Is this still an issue?
Reporter | ||
Updated•8 years ago
|
Flags: needinfo?(shobson)
Comment 2•8 years ago
|
||
Yes. Just tried it and it took 45 seconds.
Updated•8 years ago
|
Flags: needinfo?(shobson)
Comment 3•8 years ago
|
||
This is exactly the problem I have right now. foreman start doesn't work for me because it times out and thus restarts the gunicorn process so the page never gets served. I have to run "./manage.py runserver" or "gunicorn ..." by hand outside of foreman. If I change django-pipeline so that PIPELINE_ENABLED = True, then it renders in under a second.
Comment 4•8 years ago
|
||
My bad--I misunderstood this. I didn't realize stylus files were being generated outside of django-pipeline. Disregard my comment #3.
Comment 5•4 years ago
|
||
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•