1 of 1 people found this helpful
One way to get more insight into the bottleneck is F12 Developer Tools on the browser and check the timings in the Network tab. You'll probably need to send this to TechSupport if there are any obvious indications from these logs.
The 40 Table Lookup DR's can be troubling, as it can take longer to retrieve data from SQL than PI. I also don't believe Table Lookup DR's are optimized for any kind of "bulk" call to SQL. I would check how long it takes to view the attribute data from PI System Explorer on the Coresight machine. That's probably a lower-bound for what can be expected in terms of timing.
Excellent! I vaguely remember that F12 function in IE. It actually looks better in FireFox. And you can vie the code behind, sortof.
Good luck! Performance issues are time-consuming.
Virtual servers should not make a significant difference over a physical box! Can't remember the last time i've seen any physical box.
Table lookups are suspicious, but as the Asset Tree is slow too this is less likely to be the only cause. That one is easy to check by using PSE on the CoreSight server. No guarantees, but gives you some clue if it's only CoreSight or deeper.