...
Date | Compile Time | Generated Assets | Changes | ||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2017-11-10 | 5:14 / 11:58 | 343M / 838M | (baseline) | ||||||||||||||||||||||||||||||||||||||||||||||||||
2017-11-17 |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
Possible work items:
- Combine SASS compilation steps so we're not recompiling the same shared assets between LMS and Studio.
- Extract and isolate vendor JS files so that they aren't constantly re-processed by our pipeline.
- Investigate current "ideal" Bootstrap CSS compile performance (no v1 or v2 CSS code), to make sure < 1s latency is achievable.
- Change how Webpack configuration is extracted so that we don't waste so much time waiting on edx-platform to start up and give us a config value. (Complicated by Studio's git-hashed based static dir location.)
- Studio/LMS asset unification – need to discuss this. Studio assets are mostly a subset of LMS assets with slightly different path information due to the prefix. Could potentially cut a lot of the redundant processing, but we have to make sure it's aligned with the goals of SFE and other efforts.