Do you want to request a feature or report a bug?
What is the current behavior?
We are unsure if this is a combination of both webpack and webpack-dev-server. So posting here first
webpack-dev-server process is a memory hog. As of Feb 22nd it is coming in at 751.9MB for the CE branch. This is after having removed the
imports-loader plugin in Issue 9123 and before this it was often as high as 850MB.
If the current behavior is a bug, please provide the steps to reproduce.
GitLab Issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/28557
This seems really excessive and we are trying to ascertain the root cause of it. This issue will serve as a place to discuss and chronicle our attempts to alleviate this memory footprint.
I think there are a few things worth trying:
- Try exempting
devServer.watchOptions(suggested by Kees Kluskens)
- Test out this webpack PR meant to improve memory use (suggested by Kees Kluskens)
CommonsChunkPluginto prevent multiple copies of Vue from being retained in memory
- Reduce the number of babel plugins we use by replacing
What is the expected behavior?
That our dev server should not have such a large footprint
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Can ask other people that use the GDK to tell us what their mem footprint is on Linux as well if need be.