> Kelly,
>
> A few others have reported similar problems. I've tested the map in
> an environment with ten or fifteen Locations, each with a few hundred
> devices, each with several interfaces, randomly interconnected; that
> took fourteen seconds. When I restricted zDrawMapLinks to networks I
> knew spanned Locations, it took just over 1 second.
>
> So clearly there's some aspect of a very common setup that I didn't
> envision during this testing. Can you possibly be more specific? Do
> you just have /Locations with some sub-Locations, and you add devices
> to them one by one?
>
> Perhaps we could do some more extensive debugging via email. I am as
> yet unable to reproduce this problem, and I'd very much like to.
Ian,
I'm certainly willing to work on this via email, just contact me
privately, once we work through the issues we can update the list.
I have no sub locations and I added 14 devices to the location
at one time. I did try reloading the page several times over a period
of hours with no performance improvement.
This may (or may not) be the time to raise another question,
which is that we have multiple sites connected via VPN tunnels and I'd
like to draw links on the map between sites based on the status of those
tunnels, but each location is it's own subnet and the doc says that
links are drawn between devices in the same network....
-Kelly
>
> -- Ian
>
> On Oct 19, 2007, at 7:46 AM, Kelly F. Hickel wrote:
>
> > Hi All,
> > I just upgrade our server to 2.1, and I noticed some pretty
> > drastic performance hits when I put devices into locations. I've
> > turned
> > off the zDrawMapLinks for all networks, so that's not the problem.
> > This
> > is on a pretty fast, lightly loaded Centos 5 server.
> >
> > I have 5 locations defined and when I load the dashboard view
> > from the point where firefox says contacting goole maps to the point
> > where the map is fully drawn with the locations on it takes under 5
> > seconds if there are no more than one device defined in any
location.
> > If I add 14 more devices to one of the locations that time goes up
to
> > around 15 seconds.
> >
> > It seems to me that the thing that's taking time is likely to be
> > figuring out the highest level event for each location, but my
> numbers
> > seem to indicate that the map won't scale very well.
> >
> > Are other folks seeing similar numbers?
> >
> > Thanks,
> >
> >
> > --
> >
> > Kelly F. Hickel
> > Senior Product Architect
> > MQSoftware, Inc.
> > 952-345-8677 Office
> > 952-345-8721 Fax
> > [EMAIL PROTECTED]
> > www.mqsoftware.com
> > SEE BUSINESS WORK
> >
> >
> > _______________________________________________
> > zenoss-users mailing list
> > [email protected]
> > http://lists.zenoss.org/mailman/listinfo/zenoss-users
>
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
