[
https://issues.apache.org/jira/browse/IGNITE-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963628#comment-14963628
]
Pavel Tupitsyn commented on IGNITE-1665:
-----------------------------------------
Reads can have fields in different order, we may want to keep separate
TypeStructure for reads and writes
> .Net: Cache field IDs when deserializing objects.
> -------------------------------------------------
>
> Key: IGNITE-1665
> URL: https://issues.apache.org/jira/browse/IGNITE-1665
> Project: Ignite
> Issue Type: Task
> Components: interop
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Fix For: 1.5
>
>
> Profiliing deserialization of test "Address" object shows that we spend
> considerable amount of time (10-20%) inside field ID calculation.
> We already optimized this for writes using serialization "paths" concept
> where field hashing is replaced with strings reference equality checks. The
> same thing should be done for reads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
