-
Notifications
You must be signed in to change notification settings - Fork 328
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
Performance Issues #12
Comments
Well, node environment consumes more resources by its nature but 15% is really huge for a desktop machine. I tried in |
Sure thing, regarding the Raspberry Pi here is my version/kernel: pi@pivpn:~ $ node -v pi@pivpn:~ $ npm -v pi@pivpn:~ $ uname -a nodejs is for armv6 installed. Had to download the archive since the raspberry pi version in the repo wouldn't work. |
Performance is about at 1.5% on an i7 4770k @ 4.0GHz but it is enough to fully utilize the CPU on a Raspberry Pi OC'd to 1GHz. Is this just an issue with node? |
I tried in Raspberry Pi Zero: it consumes 100% CPU and makes it totally unresponsive. It is due to rendering routine. In every rendering cycle, bitmap is converted into unicode characters and updated in the terminal. It takes takes too much CPU time. Possible solution/workaround ideas:
What do you suggest? |
Options for #16 are a good choice in my opinion from the features and performance perspective. Is there any way to optimize the rendering routine itself to be less CPU intensive (or would that require blessed)? I'd also say rendering rate option could be lumped into #16 in addition to the command line options. Unfortunately, I am not a NodeJS expert so I cannot give much insight there. :( |
Hi, |
On Scaleway machines, |
This tool is very cool. What a pitty that we can't really use it because of this performance issue :( . Most companies do not allow the use of monitoring tools that have such high resource usage. |
https://github.com/ClementTsang/bottom is a nice alternative. |
I installed gtop on OSX and Raspberry Pi and I noticed very high cpu usage comparable to other monitoring solutions (htop using 1% or less). Raspberry Pi was sitting at 100% CPU utilization just for gtop and OSX was anywhere between 5-15% CPU usage at any given time. Are performance improvements on the roadmap?
The text was updated successfully, but these errors were encountered: