[
https://issues.apache.org/jira/browse/DERBY-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262784#comment-13262784
]
Rick Hillegas commented on DERBY-4280:
--------------------------------------
Hi Kim,
These changes look good. I agree that the Developer's Guide doesn't have any
pre-existing sections which fit this topic. I think your additions to the
Reference and Tuning guides are sufficient.
Some other comments follow...
rrefproperstatementcachesize:
statements kept in memory -> prepared statements kept in memory
I would add more description to the Function section:
"For more information on the statement cache, see the 'Using the statement
cache' subsection of the Derby Tuning Guide.
This property controls the number of pre-compiled statements which Derby keeps
in its statement cache. Consider raising this number if statement preparation
is taking too much time."
If you are going to include the paragraph about setting the property to 0, then
I would add a comment to DERBY-4279 so that we will remember to remove that
paragraph after we fix that issue.
ctundepth32379:
Similar comments: The real point of adjusting derby.language.statementCacheSize
is to reduce the amount of time spent preparing statements. The property lets
you balance preparation time against the memory consumed by pre-compiled
statements. Setting the property to 0 is a hack which works around the bug
described by DERBY-4279. When that bug is fixed, we should stop talking about
the hack.
Thanks,
-Rick
> Property not documented - derby.language.statementCacheSize
> -----------------------------------------------------------
>
> Key: DERBY-4280
> URL: https://issues.apache.org/jira/browse/DERBY-4280
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.5.1.1
> Environment: N/A
> Reporter: Jeff Stuckman
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-4280.diff, DERBY-4280.stat, DERBY-4280.zip
>
>
> The property derby.language.statementCacheSize is not documented in any of
> the Derby documentation.
> This property may be useful for tuning Derby.
> In addition, setting this property to 0 is vital for working around
> DERBY-4279, and its lack of documentation makes it more difficult for users
> to discover this workaround.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
