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 2010/03/24 18:45:27 UTC
[jira] Created: (UIMA-1749) UIMA AS uses one instance of a
Serializer object
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
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.
[jira] Closed: (UIMA-1749) UIMA AS uses one instance of a
Serializer object
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ 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.