Skip to content

[Bug] running dev task is too resource-heavy #420

@marcinkrasowski

Description

@marcinkrasowski

Describe the bug
Currently, when running dev task there is a huge CPU/RAM spike due to a large number of Node.js processes that are spawned, for each of the persistent apps (api-harmonization and `frontend) and also each package (blocks, framework, utils etc). These processes are used to watch for file changes in each packages and rebuild them when changes occur.

This can cause in extreme cases (like running a few browsers in the background or using a resource-heavy IDE) to OS to freeze up, which obviously is not a desired effect.

To Reproduce
Steps to reproduce the behavior:

  1. Start the dev task npm run dev
  2. Check system CPU/RAM load and notice huge spikes

Expected behavior
Running the dev task should be as light on resources as possible, definitely without causing the OS to freeze.


This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #420 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @marcinkrasowski (replace 20 with the amount, and @marcinkrasowski with the user to tip).

📖 If you want to learn more, check out our documentation.

Metadata

Metadata

Labels

bugSomething isn't working

Type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions