You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2020/08/12 12:24:00 UTC

[jira] [Commented] (TINKERPOP-2398) Kryo serialization so slow

    [ https://issues.apache.org/jira/browse/TINKERPOP-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176310#comment-17176310 ] 

Stephen Mallette commented on TINKERPOP-2398:
---------------------------------------------

This looks like it is fixed in Kryo 4.x, but Gryo is built on Kryo 3.x which means that if we upgrade we would lose compatibility as per:

https://github.com/EsotericSoftware/kryo#kryo-versioning-and-upgrading 

and specifically:

> The major version is increased if serialization compatibility is broken. This means data serialized with a previous version may not be deserialized with the new version.

is that your understanding as well? If so, then we would need to stamp out a Gryo 4.0 which would then be marked as incompatible with Gryo 3.0/1.0. I'm not sure we would bother to do that as we've already deprecated Gryo usage in Gremlin Server in favor of GraphBinary. 

> Kryo serialization so slow
> --------------------------
>
>                 Key: TINKERPOP-2398
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2398
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: io
>    Affects Versions: 3.4.8
>            Reporter: Pavel
>            Priority: Major
>         Attachments: image.png
>
>
> TInkerpop has old version of kryo dependency. That old version has bug which slow down serialization process, more info https://github.com/EsotericSoftware/kryo/issues/558
> When project so big IdentityObjectIntMap grow up to Integer.MAX and clear method eat all of CPU



--
This message was sent by Atlassian Jira
(v8.3.4#803005)