So, I'm trying to figure out why my Orion install is basically unstable. In the process of tuning a million things I'm trying to set up custom views for individual sub-organizations at my company.
I've created a page that has:
All Groups component
All Nodes - Tree
Active Group Alerts
Groups with Problems
Interfaces with High Percent USage
Last XX Group Events
and that's it. Meanwhile, I tried turning on hubble for these pages and HOLY CRAP does hubble spit out a ton of "This page is bad!" kinds of warnings. I've tried using view limitations for the page and account limitations, but in both instances it appears that both a: queries run across *all nodes* instead of the specified limitations and b: the pages run horribly.
Question becomes twofold:
What is the most query-friendly way to display this data? What components should I be using to display the components I've selected above? Is there an actual bug with some of these components?
Here are some examples of what hubble spits out, repeated about 25-40 times. I think this is a part of all nodes tree.
Admin:
116 0.64 Web SQL SELECT DISTINCT Status FROM Nodes WITH (NOLOCK) WHERE Nodes.Branch_Nodes=@Branch_Nodes (Branch_Nodes=$branchname1)
Show Stacktrace
117 0.63 Web SQL SELECT DISTINCT Status FROM Nodes WITH (NOLOCK) WHERE Nodes.Branch_Nodes=@Branch_Nodes (Branch_Nodes=$branchname2)
Show Stacktrace
Obviously I removed the names of the branches that identify my company, but you get the gist.
User (acct filter):
0.90 Web SQL SELECT DISTINCT Status FROM Nodes WITH (NOLOCK) WHERE ((((Nodes.NodeID IN
(240,221,294,718,732,833,915,916,1284,1415,1426,1461,1281,1282,1283,1285,1777,1778,1779,1809,1810,1805,1806,1852,1853,1854,1855,1856,1857,1858,1859,1860,1895,1896,1899,1900,1904
AND Nodes.Branch_Nodes=@Branch_Nodes (Branch_Nodes=$branchname1)
Show Stacktrace
19 1.12 Web SQL SELECT * FROM [dbo].[ExpandedLimitations] WHERE [LimitationID] = @limitationId (@limitationId=28)
Show Stacktrace
20 0.69 Web SQL SELECT DISTINCT Status FROM Nodes WITH (NOLOCK) WHERE ((((Nodes.NodeID IN
(240,221,294,718,732,833,915,916,1284,1415,1426,1461,1281,1282,1283,1285,1777,1778,1779,1809,1810,1805,1806,1852,1853,1854,1855,1856,1857,1858,1859,1860,1895,1896,1899,1900,1904
AND Nodes.Branch_Nodes=@Branch_Nodes (Branch_Nodes=$branchname2
cobrien is this worthy of opening tickets on? I'm no SQL master but it seems possible that pages may not be coded all too well behind the scenes.