Trick of the day: how to handle slow rendering portal pages
By Craig Harding, Consultant for PerformanceG2
Slow rendering portal pages?
If you are having trouble getting your portal pages to render in a decent amount of time here is a little trick that can greatly improve performance.
When rendering a report in Cognos viewer portlet, in a portal page, the hour glass may just spin and spin. If the report runs fine on its own and is only slow in a portal page, then try this: instead of using a Cognos viewer portlet to render the report, use an HTML viewer portlet instead. I have used this technique for a dramatic increase in performance with multiple clients.
Stay tuned for more “tricks of the day” blog posts through out the next couple of months!
February 4th, 2010 at 10:59 pm
Looks forward to more posts on on portlets and portlets performance.
December 2nd, 2010 at 12:26 am
hi,
I’ve built a portal page with two columns, a cognos navigator to the left and a cognos viewer (display report) to the right. The two columns are connected by the same channel name. If I run a report by clicking in the navigator to the left, the report is displayed to the right. It works fine with the combination of “cognos navigator” and “cognos viewer”. But the performance is not good enough.
I found an article you wrote.
http://performanceg2.com/2010/02/04/slow-rendering-portal-pages/
Could you please advise me how to communicate “HTML viewer” with “cognos navigator”?
Thank you very much!!
December 2nd, 2010 at 4:08 pm
Thank you for your interest in our article.
Properties of the report that you want to render. Copy the search path. Pass that to the HTML viewer.
I hope that helps!
Thanks,
Craig Harding
PerformanceG2, Inc.
December 8th, 2010 at 12:52 am
Thank you for your reply.
Could you tell me more about “the search path”? And how can “cognos navigator” communicate with “HTML viewer”? “Cognos navigator” can interact with “cognos viewer” just via “the same channel name”.
Please advise!! Thank you!!