Quantcast
Channel: THWACK: All Content - Network Performance Monitor
Viewing all articles
Browse latest Browse all 21870

Inner Group Creation Slowness

$
0
0

What I mean by Inner Groups is groups that are not root groups and resides within other groups.

 

I have been trying to use layered/tiered groups (root group -> location -> prod/dev -> etc.) for better organization, dashboard functionality, and reporting purposes.

Basically I wanted it to appear like the trees of All node/all applications except without the 3 level limit and with groups (so I can have node + app + components in one resource).

 

However, the creation of this has become unbearably slow.

The wait time for a root group may only take 5-15 seconds to create and load back to the manage groups page.

The wait time for a group say, 3-4 levels down, takes ~5 minutes and possibly freezes the web console page loads for everyone during that time.

This slowness seems to be the equal regardless if you are creating and add the objects at once or just moving a root group to a inner group.

After it has been created, I don't really see any issues.

 

On our environment, it is currently still just a single server + database architecture with only <300 nodes and <3000 elements.

 

We have roughly 40 groups created but it has gotten to a point where we are thinking about abandoning groups altogether and just making do with custom properties.

 

The questions I have are:

What has other people done in regards to layered tiers?

     Just stick with custom properties?

     Make the name/cp a long string with various codes (ex: us-abc-yyy_zzz)?

 

Can someone else test on their environments if they also have difficulty creating inner groups as compared to root groups?

To best duplicate it, please create at least 4 layers down, and have the lowest groups contain some applications or a simple dynamic query.


Viewing all articles
Browse latest Browse all 21870

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>