Non-responding browser

Hi!
We have a problem with using mango, and it occurs whenever showing the point list. When, for example, we are showing the watchlist the browser hogs all the cpu resources and becomes unresponding. It might be that we use quite a lot of points, but is there any way to counter this behaviour? And what hardware is needed on a administration console?

/Joakim

This message was edited 1 time. Last update was at 28/05/2008 22:23:01

Hi,

There are a couple of things to look for when you see unresponsiveness. The quantity of points should not be so much of an issue (unless you're talking thousands). It has more to do with the number of readings in the database. The initial load of a watch list may be slow while Mango caches data. Subsequently things should be ok.

The other culprit is charts that display large numbers of readings. For example an image chart that needs to plot thousands of readings and update every minute might appear slow.

Overall, i'd check the frequency at which you are taking readings (remember, once a minute means 43K a month), and the duration you are using in charts.

This message was edited 1 time. Last update was at 04/06/2008 06:38:37

We do have a lot of points, one instance with ~1100 points and one with ~700 and both of them are really slow when loading the watchlist page. To the point where browsers gives a nonresponsive script warnings. Most of the poits (~90%) have logging disabled. can some thing be done about this?

An idea for comming versions is to just load the watchlists and only load the whole pointlist when one wants to create a watchlist.

To be able to decide what page is loaded after login would also be a good thing imho.

/T

Thanks for the suggestions. We'll add them to the list.

This message was edited 1 time. Last update was at 04/06/2008 09:46:06

BTW, with that many points it may be prudent to distribute points between more Mango instances. Then, you can create a "master" instance that collects aggregated information from the cluster. The data publisher functionality can help you achieve this.