Apache OpenOffice (AOO) Bugzilla – Issue 16897
website not reachable / not responsive
Last modified: 2004-03-16 19:44:49 UTC
Hi, Additionally to the issuezilla performance issue 14352 we today experienced, that the site was not reachable / not responsive. We are aware that the OpenOffice.org 1.1RC launch generated much interest, but would like to avoid this situation with future releases (1.1 final, ...). Are there any plans (including timeframes) to improve the overall performance? Are there any bottlenecks we could avoid, a way to distribute the load to several machines, ...? Thanks, Stefan
Hi Stefan, Our operations team has been loooking into this problem this morning and I should have a report on any work that has been done and the next steps soon. Thanks, Kristen
Referencing internal tracking number, PCN 20501.
Update: CollabNet Operations has been working on the service degradation resulting from heavy access following the Openoffice 1.1 RC release. Action Plan: Operations has reviewed the most frequently requested files and staticized as many as possible, as opposed to having them go through the jvm, to help alleviate any bottlenecks. Most of these were done in advance. Next Steps: Requesting a new apache rpm so that we can raise the MaxClients setting. Next Update: By end of day tomorrow. Thanks, Kristen
Update: Engineering Management is reviewing solutions. Action Plan: Requested an ETA on the new apache rpm to raise the MaxClients setting. Next Update: By end of day Friday. Thanks, Kristen
Referencing new internal issue numbers: PCN 20619 (core product issue), PCN 16219 (new rpm for current openoffice.org).
Update: The new rpm for the openoffice.org (current version) has been prepared. Action Plan: Confirming roll out plan with operations. This should only require a sandbox restart for which we normally plan on a 15 minute time window when service may be interrupted. Next Update: By end of day Monday. Thanks, Kristen
Update: The new rpm will be put in place on Friday July 25 between 4 and 4:15 pm PDT. Thanks, Kristen
Update: The MaxClients setting has been increased and the sandbox restarted as planned. Thanks, Kristen
Hi Stefen! Did you find any improvements sfter the increases in the mysql max_connections to 1000 and the Apache MaxClient setting to 400? Thanks, Priya.
The problems occurred during heavy load. Values for the peaks during the 1.1RC release are more than 2,000,000 accesses per day and 130,000 accesses per hour. At the moment during summer vacation time we have max. about 1,500,000 acceses per day and 86,000 access per hour. So, I can't tell you, whether the site will be able to handle the upcoming peaks during the 1.1 release. Greetings, Stefan
closing
closed