I know that this IDEA is pretty much general in shape, but i am still adding it because of the feedbacks from multiple customers and personal experience. I am sure if someone can fix such small small things, it really have a good impact on user satisfaction. Not to mention we have a lot of features which we cant even compare with any other tools in the market. But the users who earlier was using OMW & OMU (especially the NOC people) who work with event browser, for them OMi is very much slow when it comes to the UI side. I will list down some of the major part which will need a UI response testing.
1) Event browser - when we double click the event browser to see event details, it comes very slow with a loading icon, but same data loads much faster when we use Event browser with details included (Another component)
2) Right clicks on top views - Response of right click on CI to see the details is terribly slow, especially when the view which we create have many relationships. I have seen it take exactly 32 seconds for a single right click response on a view ( Layered view ) with many relationships.
3) Monitored nodes - This page still use Java i believe, but showing a 1000 nodes screen takes pretty much time
4) Performance perspective - This is faster, but gets slower with more number of metrics on the same dashboard.
Also i have seen, the response time of UI is different due to network difference ( Internal subnet and external ), Also due to Windows admin policies. So its better if we can provide some instructions for the best performance of our tool. If any one else have faced such issues, feel free to add their comments.