You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2015/10/23 10:41:27 UTC

[jira] [Created] (IGNITE-1779) .Net: Evaluate BinaryFormatter overhead for generic collections.

Vladimir Ozerov created IGNITE-1779:
---------------------------------------

             Summary: .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
            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)