uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Closed: (UIMA-1749) UIMA AS uses one instance of a Serializer object
Date Wed, 24 Mar 2010 18:05:27 GMT

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

Jerry Cwiklik closed UIMA-1749.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3AS

Added a cache object to create and cache an instance of a Serializer object for each thread
processing remote CASes. The Serializer instance is cached using a thread id. This effectively
dedicates a unique instance of Serializer to each thread processing a CAS allowing concurrency
during serialization and deserialization of CASes. 

> UIMA AS uses one instance of a Serializer object 
> -------------------------------------------------
>
>                 Key: UIMA-1749
>                 URL: https://issues.apache.org/jira/browse/UIMA-1749
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>    Affects Versions: 2.3AS
>            Reporter: Jerry Cwiklik
>             Fix For: 2.3AS
>
>
> There is a single instance of a Deserializer object processing incoming CASes and also
a single instance of a Serializer object processing outgoing CASes. This may bottleneck UIMA
AS Service when handling large CASes and multiple threads are processing incoming and outgoing
CASes. It would be more efficient to create and dedicate an instance of a Serializer/Deserializer
to each processing thread so that multiple CASes cas be serialized/deserialized at the same
time. 

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


Mime
View raw message