Issue #6828 has been updated by Nigel Kersten. Status changed from Unreviewed to Accepted
---------------------------------------- Bug #6828: Dashboard takes too long to remove a node https://projects.puppetlabs.com/issues/6828 Author: Randall Hansen Status: Accepted Priority: Normal Assignee: Category: Target version: Keywords: Branch: Affected URL: Affected Dashboard version: 1.0.4 Deleting a node takes too long. A probable cause is that Dashboard deletes node reports one at a time, rather than in a more efficient manner. Here's the user's report: Subject: [Puppet Users] pupet dashboard taking more than 10 minutes to destroy a node I've noticed that puppet-dashboard takes a lot of time to refresh some webs, but today, I've started to remove some old nodes and it takes more than 10 minutes to remove one. The host hasn't a really high load: [root@puppet01 ~]# uptime 16:54:31 up 14 days, 5:17, 1 user, load average: 1.67, 1.48, 1.08 [root@puppet01 ~]# free -m total used free shared buffers cached Mem: 2026 1890 136 0 4 266 # grep -c "^proc" /proc/cpuinfo 2 and, obviously, ruby & mysql are eating all the cpu: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 31770 mysql 22 0 138m 28m 4616 S 117.2 1.4 18:42.69 mysqld 5111 root 16 0 861m 839m 2492 S 1.0 41.4 931:05.87 ruby Anyone notices this behaviour? any advice for solving this? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
