Issue 42766 - OOo site unusable slow
Summary: OOo site unusable slow
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Website general issues (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
: 42612 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-02-14 17:00 UTC by Martin Hollmichel
Modified: 2007-02-14 23:34 UTC (History)
6 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
request respone time graph (8.72 KB, image/gif)
2005-02-16 11:09 UTC, stx123
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Martin Hollmichel 2005-02-14 17:00:36 UTC
for a few hour now, the OOo site is very slow, e.g.

* a cvs commit will last between 8 and 30 seconds (compared with max 2 sec)

* access of IssueTracker pages and issue update are also in that time.

the current status is close to site down, for this set prio to 1.
Comment 1 Unknown 2005-02-14 17:27:40 UTC
Looking into this. The site seems to be working fine now. Reducing priority to 
P2.
Comment 2 Unknown 2005-02-14 19:33:13 UTC
Actually reducing the priority to P2. All components are working fine. Please 
let us know if you encounter the site slowdown.

Comment 3 Unknown 2005-02-14 20:50:26 UTC
The site has no issues right now. Reducing to P3.
Comment 4 Martin Hollmichel 2005-02-16 07:29:06 UTC
is there any news about this issue now ? Issuetracker actions are painfully slow
att his time again. I assume, 102000 guest session are too much for the site ?!
Comment 5 stx123 2005-02-16 11:09:09 UTC
Created attachment 22698 [details]
request respone time graph
Comment 6 stx123 2005-02-16 11:11:16 UTC
Please have a look at the attached graph. It shows the degradation of response
times from 2 secs to 6-18 secs (averaged!). In pratice this means that servlet
based operations like IZ we unusable Saturday afternoon and Monday evening.

The webserver logfile analysis provided no obvious root cause to me. Please
advise what the root cause could be and how we can avoid these situations.
Comment 7 Unknown 2005-02-17 01:38:25 UTC
Looking into this.
Comment 8 stx123 2005-02-17 13:06:06 UTC
*** Issue 42612 has been marked as a duplicate of this issue. ***
Comment 9 Unknown 2005-02-18 20:51:15 UTC
I need a clarification on the attached graph. 
Which openoffice page is used to graph this ?

If there is a high user activity around that time, the performance will take a 
hit. However it will still be useful to know which page is question is used 
for the graph.
Comment 10 stx123 2005-02-19 15:54:16 UTC
This graph is for the URL
http://www.openoffice.org/issues/show_bug.cgi?id=10000

But a graph for
http://www.openoffice.org/about.html (staticized page)
looks similar.
Comment 11 Unknown 2005-02-28 22:35:05 UTC
Verified that none of the graphs at CN end matched up with those that were 
attached.

Is it possible there were some network issues when this graph was plotted, 
especially since a staticized page shows similar performance?
Comment 12 stx123 2005-03-01 14:10:24 UTC
We don't see network issues from here to the network the openoffice.org and
netbeans.org site are located in. At leat the monitoring of netbeans.org didn't
show any problems at the time openoffice.org was slow.
Comment 13 Unknown 2005-03-17 22:53:16 UTC
Stefan,

Is this still an issue?
Trying to get up to speed on this one, the Internal PCN is closed as WORKSFORME.
Thanks
Comment 14 stx123 2005-03-31 13:46:13 UTC
There are several issues.
The inattentive handling of a staticization request issue led to the problem.
We still have no access to the monitoring site to compare the site performance 
data with the attached graph.
We still experience performance degradation from time to time albeit not as bad 
as during the OpenOffice.org 2.0 Beta release.

Besides that feel free to close the issue if you don't have means to detect and 
root cause performance problems.
Comment 15 Unknown 2005-04-19 00:25:54 UTC
The monitoring site should now be available to you (Issue 43820).
Closing this issue.
Comment 16 Unknown 2006-11-06 12:06:54 UTC
Could we close this issue since the 43820 has also been resolved .
Comment 17 stx123 2006-11-15 21:25:18 UTC
closing...