[
https://issues.apache.org/jira/browse/CLEREZZA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053215#comment-13053215
]
Daniel Spicar commented on CLEREZZA-564:
----------------------------------------
Before we close this issue we I would like to know if a scheduling mechanism
for optimizations should be implemented. If so, it may be good to create a
service in Clerezza that allows to Schedule arbitrary jobs as I don't think it
should be the responsibility of GraphIndexer or exclusive to CRIS.
Also, as mentioned on the mailing list we should further improve the
optimization process but because of concerns for stability I suggest to do this
step by step after verifying that current changes have not affected stability
negatively.
> CRIS: call optimize in an extra thread
> --------------------------------------
>
> Key: CLEREZZA-564
> URL: https://issues.apache.org/jira/browse/CLEREZZA-564
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Tsuyoshi Ito
> Attachments: ZZ-564-rdf.cris.core-optimize-20110622-patch.diff
>
>
> Comment from Tommaso (see
> http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201106.mbox/%[email protected]%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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
