[
https://issues.apache.org/jira/browse/DERBY-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798791#action_12798791
]
Kim Haase commented on DERBY-3259:
----------------------------------
Thanks very much for picking this up, Bryan. The new topic is very clear and
well-written. I have only a few minor non-technical suggestions.
In the new text in "When cardinality statistics go stale", I'd suggest changing
"info" to "information" where it occurs, to be consistent. Also, at the end of
the second new paragraph, "procedures" should be changed to "procedure", since
you're advising them to run one or the other procedure, not both.
In the new topic, you might want to add an indexterm or two, just in case we
are ever able to generate an index. Also, it seems polite for links to other
topics to include the title of the topic in the link, just so that users know
where exactly they are going. It's a matter of taste, though.
> Tuning manual needs performance tip on compressing tables
> ---------------------------------------------------------
>
> Key: DERBY-3259
> URL: https://issues.apache.org/jira/browse/DERBY-3259
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.3.1.4
> Reporter: Kim Haase
> Assignee: Bryan Pendleton
> Attachments: ctunperf25864.html, ctunperfstatistics.html,
> ctunstats849505.html, docs.diff
>
>
> The "Performance Tips and Tricks" section of the Tuning Derby manual needs a
> topic that recommends the use of the SYSCS_UTIL.SYSCS_COMPRESS_TABLE
> procedure to resolve performance problems having to do with indexes and
> complex table joins. (Please rephrase this if I haven't put it correctly.)
> For details, see the discussion at
> http://www.nabble.com/Re%3A-FW%3A-Advice-on-*very*-badly-performing-query-tf4939807.html.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
