You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2008/10/23 22:26:44 UTC

[jira] Updated: (UIMA-1211) Optimize UIMA-AS Logging by Testing The Log Level

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

Jerry Cwiklik updated UIMA-1211:
--------------------------------

    Attachment: uimaj-as-jms-UIMA-1211-patch.txt
                uimaj-as-core-UIMA-1211-patch.txt
                uimaj-as-activemq-UIMA-1211-patch.txt

Added a test for current Log Level before each logging stmt in UIMA-AS code.

> Optimize UIMA-AS Logging by Testing The Log Level
> -------------------------------------------------
>
>                 Key: UIMA-1211
>                 URL: https://issues.apache.org/jira/browse/UIMA-1211
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Priority: Minor
>         Attachments: uimaj-as-activemq-UIMA-1211-patch.txt, uimaj-as-core-UIMA-1211-patch.txt, uimaj-as-jms-UIMA-1211-patch.txt
>
>
> Modify Uima As code to first test the log level before calling UIMAFramework.getLogger(CLASS_NAME).logrb(..). This has a potential for further performance gain while processing CASes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.