3 ms·
I have a 2017 Macbook Pro and the main project I work on brings it to its knees. This is a front end project with a nodejs graphql server, TypeScript, eslint, V
by davedx 7y ago
I have a 2017 Macbook Pro and the main project I work on brings it to its knees. This is a front end project with a nodejs graphql server, TypeScript, eslint, VS.Code, webpack. I think actually the linting is the worst CPU drain, but all in all with the graphql server and front end tooling running at once, it makes my laptop slower than running the .NET core back end it connects to.
Kind of annoying. Working with a simple create-react-app project with TypeScript is fine though.
- ehutch79 7y agoThere's something wrong with your setup &| stack. I've run a full stack locally, a build setup with a watcher, a django/gunicorn setup with file watching, mysql/redis/rabbitmq, and i barely nudge the cpu. I'm betting your if you cpu is hot constantly while developing, it's file watching that's the issue. I had to do some work to get things to use proper file system events in macos and not just polling with my legacy gulp project. try installing fsevents if it's not already?
- revscat 7y agoThere is something wrong. I’m running two separate Rails apps, MySQL, Oracle, RabbitMQ as a broker between the two apps, Redis, and both have Angular FEs that I use VSC with. Same year MBP, and my CPU load rarely reaches 5%.
- AgloeDreams 7y agoCheck your package updates! We had the SAME issue in serving the app on macOS and no issue on windows. Updating node and updating to latest packages produced a 80% cpu drop. When I had this issue I couldn't serve the project while running VS code on my Air, the lag from input was way too bad, now it's snappy.