[jira] [Commented] (IGNITE-1665) .Net: Cache field IDs when deserializing objects.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010610#comment-15010610
 ] 

ASF GitHub Bot commented on IGNITE-1665:


Github user ptupitsyn closed the pull request at:

https://github.com/apache/ignite/pull/167


> .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: Vladimir Ozerov
>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)

[jira] [Commented] (IGNITE-1665) .Net: Cache field IDs when deserializing objects.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14964958#comment-14964958
 ] 

ASF GitHub Bot commented on IGNITE-1665:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/167

IGNITE-1665 .Net: Cache field IDs when deserializing objects.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-1665

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/167.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #167


commit 0805d6f738fe78a5618e164f8410b17b511df1d7
Author: ptupitsyn 
Date:   2015-10-19T12:12:29Z

Update benchmark

commit 3bb331d91504adcc976210161393baa68fb4f753
Author: Pavel Tupitsyn 
Date:   2015-10-19T17:20:56Z

wip

commit 68516ee3fa747018e7f2db62862caf25689032e9
Author: Pavel Tupitsyn 
Date:   2015-10-19T17:43:23Z

wip PortableStructureTracker

commit 635e19e754041351d8efe20115b79e66301d5aaa
Author: Pavel Tupitsyn 
Date:   2015-10-19T18:16:42Z

wip

commit a1647ec2d9ff026c0a0e2b0bc2a6c19e9003c904
Author: Pavel Tupitsyn 
Date:   2015-10-19T18:22:19Z

wip

commit 208383cb7c757b7ee941820450dcff601ce8d41e
Author: Pavel Tupitsyn 
Date:   2015-10-19T18:38:07Z

Reader refactoring done

commit a3861aa8048f6ff1949ed33f9587444acea4aeaa
Author: Pavel Tupitsyn 
Date:   2015-10-19T18:38:58Z

wip

commit 564726f8375dbb8156bc8d3fa75508ad7fc88444
Author: Pavel Tupitsyn 
Date:   2015-10-19T18:40:58Z

fix tests

commit eee1b7d12d2ef7be7d5d7e2b4430825a39c5ca70
Author: Pavel Tupitsyn 
Date:   2015-10-19T18:47:37Z

wip

commit 0d0289eaaa9c334707599cb5184236905a30fc06
Author: Pavel Tupitsyn 
Date:   2015-10-19T18:48:52Z

wip

commit 0d4eca8375410e526a14293dde7e892b12cd5ba5
Author: Pavel Tupitsyn 
Date:   2015-10-20T08:28:04Z

Cleanup fieldTypeId

commit 2119c5301d65bd2341d46131d6d8542a47ea1d6d
Author: Pavel Tupitsyn 
Date:   2015-10-20T08:32:12Z

wip

commit d29f04a34f3232b75b383e919b315807b5311f21
Author: Pavel Tupitsyn 
Date:   2015-10-20T08:54:21Z

Revert WriteBenchmark

commit 0231b666af134c8e03b711808cae1db2ed3fc12a
Author: Pavel Tupitsyn 
Date:   2015-10-20T09:01:22Z

PortableReadBenchmark

commit 7fd004f55ed44be3da799f64ebea898184bf9864
Author: Pavel Tupitsyn 
Date:   2015-10-20T09:03:40Z

wip

commit a4ac133930f666c734c5dfce23aa539425ebacb2
Author: Pavel Tupitsyn 
Date:   2015-10-20T09:17:30Z

wip benches

commit 9e323d290a6e874c4b8c93147d2354206d2ba574
Author: Pavel Tupitsyn 
Date:   2015-10-20T09:33:29Z

wip

commit 10ed61cb567d69770ef8b82b47174ed430027714
Author: Pavel Tupitsyn 
Date:   2015-10-20T09:58:49Z

Improve GetStringHashCode

commit 132a366fbd46ae46830fcec45a7a673383ec40c0
Author: Pavel Tupitsyn 
Date:   2015-10-20T09:59:00Z

wip

commit 75d603aa25d6398f75b76836d470ddccc0852a9c
Author: Pavel Tupitsyn 
Date:   2015-10-20T09:59:49Z

wip

commit 7f591327de92a4cf384b940b46c843607c316cf3
Author: Pavel Tupitsyn 
Date:   2015-10-20T09:59:56Z

wip

commit 7862d7a5b546c10786a2287e172105ffe3737c78
Author: Pavel Tupitsyn 
Date:   2015-10-20T10:04:19Z

wip

commit 5a7601012de1614c7b4d8f5e05982b8101594fcb
Author: Pavel Tupitsyn 
Date:   2015-10-20T10:12:46Z

wip

commit c8190a86e5c1557c12d7e7c9c556768ce2a0c0da
Author: Pavel Tupitsyn 
Date:   2015-10-20T10:23:58Z

Cleanup

commit 678e6fe6e6f825ca5a85e6d611038ff7f01173e5
Author: Pavel Tupitsyn 
Date:   2015-10-20T10:37:31Z

Cleanup




> .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 

[jira] [Commented] (IGNITE-1665) .Net: Cache field IDs when deserializing objects.

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)