What does each Meteor process do?
New to Meteor and not very good with Linux here. In Meteor v1.0.1 - development mode. When I start top
, only my Meteor app is running on my server, I see three main processes associated with the app.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
15445 root 20 0 1367736 443624 2792 S 10.3 43.8 6:09.26 [dir]/.meteor/packages/meteor-tool/.1.0.36.1rumazb++os.linux.+
15517 root 20 0 830796 107040 3172 R 3.0 10.6 1:07.75 [dir]/.meteor/packages/meteor-tool/.1.0.36.1rumazb++os.linux.+
15468 root 20 0 813608 36348 1824 S 0.3 3.6 0:04.82 [dir]/.meteor/packages/meteor-tool/.1.0.36.1rumazb++os.linux.+
I want to know what these three processes are doing. Is there provision for accessing MongoDB? And what is it that takes up so much memory (444 MB)? The reason I am asking is because I ran out of memory shortage on my server and I want to get to its root.
0
source to share
1 answer
The Meteor process, which consumes 10% CPU and a lot of memory, is something that's only here for development mode. This process acts as an ongoing process to support development cycles:
- scans the filesystem and starts recompilation when modified by the developer
- resolves conflicts and package dependencies by running a constraint resolver
- proxies all requests to localhost: [port] to the application process, will not damage the connection if the application process is restarted (after recompilation)
- starts and configures MongoDB with the replica set installed (to execute a tail oplog to be executed by the application) and monitors its state
+1
source to share