puppetboard
puppetboard copied to clipboard
voxpupuli
Pagination of all views
Most views just render all available nodes at once. This is fine for smaller deployments, however if you have multiple thousands of nodes this does not scale very well.
We have an installation of 6k nodes and the node view almost kills the browser since it fetches all 6k and tries to render them. The whole frontend becomes completely unresponsive because of this.
I'm having issue with facts page that is not able to render even with hundreds nodes. It could be helpful to filter out some facts like macaddress_* to reduce cardinality. But pagination is more universal solution.
Hi @ZeroPointEnergy and @deric! Are you still having such issues with the current version of Puppetboard? Because we are using the app in env with ~3.5k nodes and although some pages do take a few seconds to load the performance is not terrible IMHO.
@gdubicki in our environment with ~11k nodes, it takes around 38 seconds to finish rendering the main dashboard on 3.3.0.
Timing is roughly 0 : request start 10 : psql returns data to puppetboard 22 : puppetboard starts sending data to client 25 : initial render completes 28 : jquery daily_reports, lists.js, tables start running 38 : jquery finishes
so it isn't all puppetdb itself but having pagination would reduce the data at all steps lowering the load times.
The nodes page loads a bit quicker, at least initially, but tends to lock up the browser trying to run the javascript.
Just adding my two cents that this is a much needed request for larger environments. I'm getting timeouts installations with a large number of loads.
