additional speed improvements for webpack #6702
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* remove prefill question * new test snapshot
This trait is calculated by the last time a student completed an activity assigned by a teacher at this school
* Fix some caching issues in the CMS * Break out of module to ensure Response called.
emilia-friedberg
changed the base branch from
develop
to
feat/upgrade-webpack
lms/add-vitally-last-active
* Install jest. * Add tests for createSession
lms/add-segment-group-call
…Core into feat/other-ways-to-speed-up-build
delete-merged-branch
bot
deleted the
feat/other-ways-to-speed-up-build
branch
emilia-friedberg
added a commit
that referenced
this pull request
Sep 9, 2020
* try committing changes * fix memory issue * memory update for prod-cms call * additional speed improvements for webpack (#6702) * Remove references to prefilledText in all LMS apps (#6693) * remove prefill question * new test snapshot * Remove leftover unused write to Firebase (#6695) * try committing everything but yarn lock * put expose loader back because it turns out we do need that * minor c hange so I can deploy again * Add a "last_active" trait to Schools when syncing Vitally This trait is calculated by the last time a student completed an activity assigned by a teacher at this school * Remove an extraneous leftover line * dumb * add check for empty questions array (#6694) * Fix some caching issues in the CMS (#6697) * Fix some caching issues in the CMS * Break out of module to ensure Response called. * Be more specific with our `maximum` call to disambiguate * remove commented out loaders * Add analytics.group calls if current_user.school exists * Tweak tests to account for in-memory vs in-db time precision * Fix the two most common LessonsServer errors and add tests. (#6707) * Install jest. * Add tests for createSession * Fix error with teacher_ids (#6710) Co-authored-by: cissyxyu <[email protected]> Co-authored-by: Anathomical <[email protected]> Co-authored-by: Eric Adams <[email protected]> Co-authored-by: dandrabik <[email protected]> * final round of improvements to our current prod webpack build (#6713) * Remove references to prefilledText in all LMS apps (#6693) * remove prefill question * new test snapshot * Remove leftover unused write to Firebase (#6695) * try committing everything but yarn lock * put expose loader back because it turns out we do need that * minor c hange so I can deploy again * Add a "last_active" trait to Schools when syncing Vitally This trait is calculated by the last time a student completed an activity assigned by a teacher at this school * Remove an extraneous leftover line * dumb * add check for empty questions array (#6694) * Fix some caching issues in the CMS (#6697) * Fix some caching issues in the CMS * Break out of module to ensure Response called. * Be more specific with our `maximum` call to disambiguate * remove commented out loaders * Add analytics.group calls if current_user.school exists * Tweak tests to account for in-memory vs in-db time precision * bunch of clean up in the webpack files * run terser plugin in parallel * start using the cache-loader for jsx and tsx files * tiny change to deploy again * get rid of cache-loader * Fix the two most common LessonsServer errors and add tests. (#6707) * Install jest. * Add tests for createSession * just remove sass-loader from evaluating .css files * Fix error with teacher_ids (#6710) * add the hard source webpack plugin * re-install terser webpack plugin * whitespace change to redeploy * get rid of stuff that really isn't helping Co-authored-by: cissyxyu <[email protected]> Co-authored-by: Anathomical <[email protected]> Co-authored-by: Eric Adams <[email protected]> Co-authored-by: dandrabik <[email protected]> Co-authored-by: cissyxyu <[email protected]> Co-authored-by: Anathomical <[email protected]> Co-authored-by: Eric Adams <[email protected]> Co-authored-by: dandrabik <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHAT
Delete all the npm packages we weren't actually using in the code; upgrade some additional packages that we use in the webpack config.
WHY
I noticed that we download all the npm packages twice during our deploy process, so reducing the number of those should help reduce our deploy time, as well as reducing the total size of our bundles. Then I updated and cleaned up the loaders we are using in the webpack builds (for instance: a loader that only existed to handle something for a package we weren't actually using). Our asset precompilation using this method went down to 756.29s, so a little more than a minute faster than the previous PR (832s), and the total deploy time is now 17 minutes, compared to 21 in the PR with the webpack improvements and 25-30 prior to that. Progress!
HOW
I started trying to just update some of the loaders we use in the webpack builds, and in the process I noticed that we had a lot of packages that just weren't getting used at all, so I updated the ones we were using, removed the ones we weren't, and then did a lot of testing on sprint to make sure I didn't break the website.
Screenshots
N/A