<p>Hi,<br />I have been a performance architect for five years now and I think maybe it's about time to share some of my experience with you, SAP customers. My hope is that this blog will increase your awareness and add to your knowledge and if, as a result of reading it, you are able to boost performance in your organization - I'll be very happy.<br /><First posting will refer you to the portal performance guide for 7.0 ><br />The idea of a portal performance guide came up as part of a project to reduce TCO for our customers. There was a clear need to create some order out of a wide variety of performance recommendations and notes. The idea was to save time for customers, to enable them to find everything in one document. So we created the Performance Best Practices Guide for SAP NetWeaver Portal 7.0, hoping that this is a big step in that direction.</p><p>While looking at customer messages about performance, I saw that most of the time is spent trying to identify the source of the problem, causing a long, ping-pong of discussions between customers and our support team. The first part of the document tries to eliminate this ping-pong phase and gives some directions about how to isolate the main suspects in your performance pain.</p><p>The second part of the document talks about the navigation cache. This cache can make miracles, but only if you use it wisely, so I recommend reading about it.<br />The third chapter reveals the portal runtime properties that can influence performance and chapter four talks about Portal Content Directory (PCD). I truly recommend reading this chapter.<br />Finally, there is a chapter about sizing.<br />You can find the document from the Best Practices - Portal page on SDN.<br />Best Practices - Portal
This is a direct link to the guide:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0f1358d-0812-2c10-b58c-c7bdd7a0c...
I worked on the performance guide together with my colleagues, portal developers, and our consultants from the field. I really hope you find it useful. I am also more than willing to receive constructive criticism. So don’t think twice about writing your opinions about the document.
