CMS Performance Issues

Hi All,

As a part of monitoring we have an Automated script that does the below set of activity and captures the time required for the same.

Steps:
1.Login into TeamSite
2. Navigate.
3. Edit / Save DCR
4. Preview
5. Submit/ Approve.
6. Logout.

We noticed that the time taken used to vary with a +- of 100 sec, but the CPU Utilization was the same. On further analysis we found that the "First byte download" used to take to much time. and generally when ever a .cfi file was involved.

We used to httpAnalyzer software for the same.

Has any one also faced similar content Issues and if yes, how can we reduce the time taken for "first byte download"

Any Help on this would be great.

Note: We have tested the same using Akamai and without it also.

Thanks
Prem Pratick Kumar

Find more posts tagged with

Comments

John742

Have you broken down the different click throughs that your PT utility goes through in this list? Have you identified one step that varies much more than the others? Also please provide informaion on your current env., specifics on how preview is set up, and how you are leveraging formspusblisher.

prem_pratick

Hi,

Our current ENV is
TS 6.1 SP2, Solaris 8. OD 6.1, iPlanet LDAP. Webdeskpro.

When a user saves/publish a DCR the values goes to the Oracle 10G DB. and the assets (Images/.pdfs) goes to the webserver. We have a weblogic plug in installed on our webserver.When Preview is clicked the URL is formed and the corresponding Page is made.

But preview of the DCR is not the bottleneck.

Our a period of time, we have noticed that the below steps take more time. {This steps sometimes take too much time and sometimes too less time}

1. Login
2. Submit of DCR.
3. Take ownership/Approve and Transition.
4. Navigating between different branches.

And in all the above steps we find that first byte download is the culprit.

We have implemented most of the IW recommendations for TS6.1 such as mod_expires/ and all.

We are having 8 CPU and 16GB RAM but I don't feel we are utilizing the same.

Thanks
Prem Pratick.