Portal EHP1 response inconsistent, where can I find performance data

Question

Currently we are running NW EP EHP1 on unix. We have noticed that when I log into portal screen and iviews paint really fast and then once in a while the screen paint slows to a crawl.
Where can we check portal permformance statistics for iview connecting back to BW, ECC and SCM.
I have noticed that some of the webgui screens in SCM takes a long time and takes a while to render to the end user.
Anyone have an idea where I can check the stats on EP.
Thanks
Weyland Yutani

Answer 1

Dear Weyland Utani,
The following factors can affect performance in the portal layer:
1. Overhead due to authentication mechanisms and the consequent delay in login
2. Time taken to connect with a back end
3. Resources consumed due to logging
4. Time taken to load home page
5. Design of Java iViews
The following factors can affect performance in the operating system layer:
1. Memory
2. CPU consumption
3. Network bandwidth
4. Java Virtual Machine (JVM)
5. The kernel
In this first step, you can ask the following questions to help you understand the problem:
a) Is the problem related to a single user?
b) Does the problem occur during heavy load conditions?
c) Does the problem occur during specific times of the day or all the time?
d) Does the problem occur only during a specific activity such as accessing a backend
system or a database?
e) Is the problem reproducible?
f) Is the problem simply poor performance or is it also accompanied by incorrect
results?
g) Does the problem occur only during logon?
h) Does the problem occur only during the first use?
i) When did this problem start?
j) Did anything change in the system, operating system, patches, or the application
before or after the problem occurred?
Moreover, you might want to check the size of the log files The log file size should not increase more than 1MB
under load. Also whether any error is being logged because of connectivity issues to any of the backend systems such as
the content management server, database, or the SAP system. Check the Windows Event Log for clues.
On the lighter side, in some cases, poor performance may be due to caching on the browser or improper proxy settings. Clearing the browser cache and accessing the portal again may be of help.
Depending on the severity level set, the log files are created. Following are the different severity levels that can be set in increasing order:
u2022 DEBUG
u2022 PATH
u2022 INFO
u2022 WARNING
u2022 ERROR
u2022 FATAL
For example, if the severity level is set at INFO, the log files include messages at the levels of DEBUG, PATH, and INFO. However, the messages at severity levels WARNING, ERROR, and FATAL are not created. The online log viewer is available in the Visual Administrator as a Log Viewer service.
HTH
Regards,
Muhammad Abdul Qawi