You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Daniel Spicar (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/26 16:12:38 UTC

[jira] [Resolved] (CLEREZZA-564) CRIS: call optimize in an extra thread

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

Daniel Spicar resolved CLEREZZA-564.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.2-incubating

While not all suggestions in the discussion are implemented (e.g. a Scheduling Service), the basic Improvement specified by this issue has been implemented. Therefore I am resolving this issue.
                
> CRIS: call optimize in an extra thread
> --------------------------------------
>
>                 Key: CLEREZZA-564
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-564
>             Project: Clerezza
>          Issue Type: Improvement
>    Affects Versions: 0.2-incubating
>            Reporter: Tsuyoshi Ito
>            Assignee: Daniel Spicar
>             Fix For: 0.2-incubating
>
>         Attachments: ZZ-564-rdf.cris.core-optimize-20110715-patch.diff
>
>
> Comment from Tommaso (see http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201106.mbox/%3CBANLkTimtPvGC3M6uW94mo1xf=eU-DYLYcA@mail.gmail.com%3E)
> A possible enhancement could be to create an OptimizeThread with a timeInterval constructor which optimizes the index, if there is not "much" activity (i.e.: analyze isLocked, InfoStream, etc), every timeInterval seconds.

--
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