db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-4940) Tune istat operational characteristics
Date Mon, 01 Oct 2012 10:05:07 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan closed DERBY-4940.
----------------------------------

    Resolution: Won't Fix

Given that we haven't gotten much feedback from users, I assume the current defaults are ok.

I'm resolving this issue as Won't Fix and closing it, but users should feel free to reopen
it or log a new issue at a later time if the defaults turn out to be problematic.
                
> Tune istat operational characteristics
> --------------------------------------
>
>                 Key: DERBY-4940
>                 URL: https://issues.apache.org/jira/browse/DERBY-4940
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.8.1.2
>            Reporter: Kristian Waagan
>              Labels: derby_triage10_10
>         Attachments: derby-4940-1a-absdiff_to_1k.diff
>
>
> The istat feature relies in a few tuning parameters to work properly.
> The main goals of the feature is to avoid stale statistics degrading query performance,
and at the same time not interfere too much with user activity. Some study of applications
"in the field" is necessary to properly size the set of parameters.
> It is also clear that it is impossible to make the feature behave exactly as wanted for
all types of applications. Users that want full control of their statistics, can disable the
istat daemon and manually monitor and update the statistics.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message