You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jim Challenger (JIRA)" <de...@uima.apache.org> on 2014/10/27 17:59:34 UTC

[jira] [Updated] (UIMA-4063) DUCC RM: run its schedule on the OR clock instead of its own

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

Jim Challenger updated UIMA-4063:
---------------------------------
    Component/s: DUCC

> DUCC RM: run its schedule on the OR clock instead of its own
> ------------------------------------------------------------
>
>                 Key: UIMA-4063
>                 URL: https://issues.apache.org/jira/browse/UIMA-4063
>             Project: UIMA
>          Issue Type: Task
>          Components: DUCC
>    Affects Versions: 1.1.0-Ducc
>            Reporter: Jim Challenger
>            Assignee: Jim Challenger
>
> This has gone back and forth over time.  At one point the OR would get 'stuck' and blast its clock many times a second so we moved RM to its own clock.  This seems to be remedied now so the RM should go back to the OR clock to increase responsiveness.  This revival includes a "blasti-guard" so RM does not schedule more often than 1 OR clock even if things go awry.
> The code for both modes is kept in the RM so its straightforward move back and forth between the modes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)