To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=56711
User asarkar changed the following:
What |Old value |New value
================================================================================
Priority|P2 |P1
--------------------------------------------------------------------------------
Summary|IZ / CVS slowness |IZ unacceptably slow at
| |times
--------------------------------------------------------------------------------
Target milestone|Patch |---
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Fri Jan 20 01:39:38 -0800
2006 -------
#1. Changing the summary to reflect the current issue and raising the priroty
to a P1; although not a site down condition, but defintitely merits the
highest priority.
#2. The last couple of days CN's internal team has been working diligently to
understand what's causing this skowdown (and near outages).
Although, a complete resolution will take some time, here are the findings and
some short/mid term steps planned to alleviate the condition.
1) Around the time when a particular serious occurence of this IZ
unavailability occured, it was noticed that a guest user ran an intensive IZ
query multiple times over a 111 minute period. This query was consistently
performing text searches for the string "ActiveConnection" on the "blob" data
of the attachments.
This query had to be built using the custom query fields in IZ. Doing text
searches on potentially binary data is not a good idea on data sets of this
size.
Although newer versions of the underlying DB used in Danube (CEE 3.5) might
offer better performance on text searchesa, in the interim engineering is
investigating whether to: remove left joins, index additional columns, remove
Attachment Data and Attachment Metadata from the custom query fields. All of
the above possible options are being tested right now in a test environment
with OO.o dataset to characterize performance with and without the attachment
data.
2) Another set of recommendations that CN engineering have provided are:
If OO.o needs to require a role assignment for accessing the IZ query page.
This is the only way to limit any inappropriate IZ usage, whether malicious or
accidental, which could cause site disruption.
They are looking into enhancements to support a couple levels of authorization
for what kinds of queries are available:
- Guest: Restricted subset of query fields
- Developer/RegisteredUser/etc: Full access
Another option would be to only allow guests to search issues using the "Site
search" feature and allow registered users to query IZ directly. From what
engineering could see in the access logs, this would either cut off a lot of
the queries or force people to sign in.
3)The 500 ISEs that the site experienced recently were also traced to happen
during the times when the "bad queries" are run. A few site parameters for the
DB, web/application server are adjusted to handle this.
The above update is by no means an exhaustive list of what the engineering
activities are around this issue, as they are still researching into various
options to improve the performance of the site.
A summary of the short/mid term steps for now:
Short Term:
-----------
- Hands on monitoring and characterization of the running site with production-
opearions personal.
- Add indexes to select columns in IZ.
- Validate and tune DB/JVM/Application server parameters
- Selective bug patches as hot spots are discovered that require code changes
- Remove Attachment data and metadata from IZ custom query fields
Medium Term:
------------
- Add role assignments for IZ query access
- Investigate alternative data partitioning schemes for OO (archive?)
- Investigate general improvements on 3.5.1
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
