frankrousseau
commented
11 years ago That's mainly a CouchdDB issue. Running a Python server sucks CPU too. That's not related to Newebe. Thank you for the report.
Closed robinbb closed 11 years ago
frankrousseau
commented
11 years ago That's mainly a CouchdDB issue. Running a Python server sucks CPU too. That's not related to Newebe. Thank you for the report.
From my post to the Google Group:
My recent Newebe installation is taking a great deal of CPU, unexpectedly.
It has been running for one week. The couchdb instance, which I installed only for Newebe, has consumed 164+ hours of CPU! This means that it has been runnable since I installed it. Is this expected? It is occupying 99M of virtual memory, and 17M of that is resident. I consider this to be very resource usage. (This is the beam.smp executable of couchdb.)
The python2 binary which is executing newebe_server.py is also taking a lot of resources - 72 hours of CPU time (in 1 week of uptime), 37M of virtual memory, and 14M of resident memory.
These 2 processes are by far the most resource-hungry on my system. (I run many things on this system - web servers, mail servers, IRC daemons, etc.)
Is this normal and expected? Or, are those processes doing too much?
Response from gelnior:
This is bad. I didn't pay attention to that because my Newebe runs on a dedicated plug computer. But as you say beam.smp use 8% of my CPU when my Newebe does nothing.
The newebe binary has a low consumption (0.3%) but works all the time.
Both of these problems probably comes from a bad usage of external libs (couchdbkit and python daemon). You can open a report too for this one.