[
https://issues.apache.org/jira/browse/IGNITE-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976342#comment-14976342
]
Pavel Tupitsyn commented on IGNITE-1779:
-----------------------------------------
Initial overhead of Serializable can be quite large, but for collections of
more than ~10 elements Serializable is more effective than our collection
marshalling (because of headers).
So I think BinaryFormatter is fine for collections.
> .Net: Evaluate BinaryFormatter overhead for generic collections.
> ----------------------------------------------------------------
>
> Key: IGNITE-1779
> URL: https://issues.apache.org/jira/browse/IGNITE-1779
> Project: Ignite
> Issue Type: Task
> Components: interop
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Fix For: 1.5
>
>
> It seems that BinaryFormatter is extreeeemly inefficient. I tried to write a
> single Guid with and it resulted in >100 bytes comparing to 16 bytes when
> written in portable form.
> If we notice the same overhead for collections/arrays which are fairly often
> used types, we will have to revert to our initial approach when collections
> were serialized using our own mechanics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
