On Mar 26, 2009, at 4:30 PM, g3vt wrote: > So I hate to bring up another "slowness" thread, but I've been > trying to track down some slow response times we're getting from our > web ui. They've been around for a while, but its finally getting > to the point of annoying. > > I've managed to isolate it to any UI interaction that hits either > the deviceSearch or the componentSearch catalogs. (Specifically > clicking from the event list to a device or component) > > If I click on the events gem to see the events for a device, its > fast and from there I can go to the rest of the device's > information- but if I click directly on a device, it can take 30+ > seconds before zenoss will take me to the devices page. > > Does anybody have any ideas on this or run into something similar?
The most common reason for a device's status tab to come up slowly is the "Availability" calculation that is done to show it in the upper- left section of that page. This looks back one week (by default) into the history table to figure out what the device's availability is. If your MySQL database is overburdened this is the first place it will show. I'd check to see how many events you have in the history table. Clean it up and run an "OPTIMIZE TABLE HISTORY" to try to improve it. Otherwise standard MySQL tuning tips apply. _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
