Re: [performancecopilot/pcp] pmwebd impossibly slow when using grafana with 300 archives (#117)

["Frank Ch. Eigler" <notifications@xxxxxxxxxx>]

So about 2 GB of data per server per day, times seven days, times 300 servers, so 4200 GB of data on disk. Wow. Even the current day's data won't fit into your machine's RAM, so any scanning would have to rely on libpcp/archive optimally using .index files to seek to just the the parts being requested by the client (pmwebd/grafana). I don't know if pcp developers have much experience with such RAM-starved configurations.

This is not to say it's hopeless. I'd start with a highly constrained grafana query (substituting PMWEBD and HOSTNAME). It represents kind of the best case - one archive file, small time slice from the end. If that works, try additional &target= clauses, or gradually relax the host wildcard (so as to select more hosts).

http://PMWEBD:44323/grafana/index.html#/dashboard/script/multichart.js?from=now-5m&to=now&target=*HOSTNAME*.kernel.all.load.1%20minute&title=kernel.all.load.1%20minute&style=json

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.