Map Cache Timeout

chris.newton

Is anyone else still having a problem trying to change the Map Cache timeout?

Admin / Web Console Settings / Map Cache Timeout

I noticed in 9.1 SP3 that when changing this value and clicking submit the original value reverted back.  I was advised this was going to be fixed in SP4.

Is it me or this still a problem in SP5? I know I can change the value in the Database but its more of an inconvenience.

Thanks

Sonic777

This is something that we have experienced as well.  There have been three things that we have done to correct the issue. 

1. Created a ticket and worked with SW on this issue, the timeout function was push out from the standard MS setting up to 6 minutes.

2. We have over 3200 nodes with over 20,000 elements that we are monitoring, we revisited our maps.  We rebuilt the structure to be standard to a wide and shallow layout.  A maximum of 5 drill-downs is all that is allowed on our maps anymore.  We have also added classifications of maps.  Location maps don't roll-up to application maps and visa-versa, component maps (i.e. all file servers in a region), don't roll-up to either of the previous.

3. We upgraded the server for the website.  We had over-burdoned the server.

To put it simple, most of out problems were created by us.  We didn't recognize the server problems that were coming, the CPU was pegged every-time one user would open our global map.  The maps were rolling up ever node multiple times.  The system doesn't cross reference for this, if your map is hosting nodes x, y, and z and it rolls-up 3 levels where you have x, y, and z again it will revalidated that information as a separate addition to that map.  This all has to do with the map "status" icons.

It may not be your issue, but it's good practice to write up a doc to limit how your maps roll-up.

I don't want to steer anyone wrong on any of these points, please can a SW correct me if I have botched anything.