Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slow and crush #5793

Open
andrewvlgafc opened this issue Mar 31, 2024 · 2 comments
Open

Slow and crush #5793

andrewvlgafc opened this issue Mar 31, 2024 · 2 comments

Comments

@andrewvlgafc
Copy link

Hello. Write message from phone

Can you help?)
Problem description here
https://stackoverflow.com/questions/78252140/pm2-problems-slow-and-crush

Thanks!

@andrewvlgafc
Copy link
Author

andrewvlgafc commented Apr 1, 2024

I uninstall nvm, nodejs, restart. insal all - problem not disappear. nodejs process of pm2 - CPU 25%, ram increasing
If in ecosystem.config.js is about 4-5 applications ram of pm2 node increased to 2.5G and crush. And all my applications is killed.
pm2 v5.3.1
nodejs V14.17.6

part of PM2 report
--- PM2 report ----------------------------------------------------------------
Date : Mon Apr 01 2024 12:23:42 GMT+0300 (Москва, стандартное время)

--- Daemon --------------------------------------------------------------------
pm2d version : 5.3.1
node version : 14.17.6
node path : not found
argv : C:\Program Files\nodejs\node.exe,C:\Users\1\AppData\Roaming\nvm\v14.17.6\node_modules\pm2\lib\Daemon.js
argv0 : node
user : undefined
uid : N/A
gid : N/A
uptime : 20min

--- CLI -----------------------------------------------------------------------
local pm2 : 5.3.1
node version : 14.17.6
node path : not found
argv : C:\Program Files\nodejs\node.exe,C:\Program Files\nodejs\node_modules\pm2\bin\pm2,report
argv0 : C:\Program Files\nodejs\node.exe
user : 1

--- System info ---------------------------------------------------------------
arch : x64
platform : win32
type : Windows_NT
cpus : Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz
cpus nb : 4
freemem : 635662336
totalmem : 8449085440
home : C:\Users\1

@andrewvlgafc
Copy link
Author

Solver !
it was because watch: '.' in ecosystem. And pm2 recursively set watch on files again and again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant