Performance tuning tips for BI 4.0 Web Intelligence
Hello Webi Gurus,
I have been working in support for over 15 years and have seen many grey areas that fall in between Product Support and Consulting. One of the most common grey areas is performance.
I’ve started a compilation of Tips concerning performance at the below link for more ideas.
Product Support’s main objective is to help uncover defects and provide customers with solutions for issues that impact their ability to utilize the full potential of their Business Intelligence deployment. Performance issues are tricky because they are not always related to defects and can spawn from a variety of scenarios and can occur at basically any of the tiers within the deployment. Quite often the performance bottleneck is related to configuration or process flow rather than a defects in the software.
An average install of BI 4.0 includes the following tiers that can contribute to performance issues while running reports:
- Client Tier (Workstation/Browser/thick client applications)
- Web Tier (Web Server, Load Balancer, Proxy/Reverse Proxy Server, Network)
- Application Server Tier
- BI Processing Server Tier (BI 4.0 Servers)
- Database Tier
We could probably even go deeper than those levels mentioned above but I don’t want to get too deep today as my main focus of this blog post will be the Client Tier.
Over the coming months, I will be writing up blog posts that cover a variety of tricks, tips and known issues that relate to performance at these different tiers. I will be utilizing wiki pages for the bulk of the content and will be using a series of blog posts to drive awareness of the wiki pages.
My first wiki post is up live now and can be found below.
The above wiki page goes into detailed steps on how you can fine tune your client machines to utilize Java caching and the Java Next-Generation plugin architecture to ensure that your end-user’s load times for the Rich Internet Applet (RIA) is as quick as possible.
It also details some troubleshooting best practices and tips for identifying bottlenecks.
I’d love some feedback on this page and if anyone has anything to add, please let me know.
Thanks for tuning in (Pun intended)