FreifunkBremen / yanic

Yet another node info collector - for respondd to be used with meshviewer to Grafana (with influxdb or graphite)
https://freifunkbremen.github.io/yanic/
GNU Affero General Public License v3.0
20 stars 40 forks source link

[BUG] Memory usage is disk usage #35

Closed xf- closed 7 years ago

xf- commented 7 years ago

Memory usage is always really high. I think it is disk usage and not RAM.

genofire commented 7 years ago

If it is the disk usage, it is not problem here.

Maybe my math for usage could be interprated on a other way (https://github.com/FreifunkBremen/yanic/blob/master/meshviewer/meshviewer.go#L74): For memory we recieve cached, total, buffers", free (https://github.com/FreifunkBremen/yanic/blob/master/data/statistics.go#L67) and for the meshviewer we calc the usage by (total- free) / total

xf- commented 7 years ago

Maybe its not the disk usage, but it always around 90% and red. Looks not so good. Cache isn't really used. I think used should be in nodes.json.

genofire commented 7 years ago

do you have ffmap-backend also running? or the statuspage of the node? how looks there?

I did not know how to handle either - ffmap-backend make it same way - https://github.com/ffnord/ffmap-backend/blob/detailed-rrds/lib/nodes.py#L93 -> 1-free/total

Do you mean we should use buffers/total ??

xf- commented 7 years ago

yanic spectacle lh5713

vs ffmap-backend spectacle kn5713

htop and other only show used as number or % in system monitor spectacle wz5713

buffers and cache can be cleaned and used otherwise then system needs the ram.

genofire commented 7 years ago

https://github.com/freifunk-gluon/gluon/blob/master/package/gluon-status-page/src/js/lib/gui/statistics.js#L241

lets try 1 - (free + buffers + cached) / total it look realistic