[ https://issues.apache.org/jira/browse/FLINK-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152448#comment-15152448 ]
Gabor Gevay commented on FLINK-3277: ------------------------------------ Ah, yes, you are right, this wouldn't work with Tuples. It would only work with POJOs having `long` fields. So, it seems that the current performance difference between Tuples and POJOs would likely get reversed after code generation in the serializers are introduced. > Use Value types in Gelly API > ---------------------------- > > Key: FLINK-3277 > URL: https://issues.apache.org/jira/browse/FLINK-3277 > Project: Flink > Issue Type: Improvement > Components: Gelly > Affects Versions: 1.0.0 > Reporter: Greg Hogan > Assignee: Greg Hogan > > This would be a breaking change so the discussion needs to happen before the > 1.0.0 release. > I think it would benefit Flink to use {{Value}} types wherever possible. The > {{Graph}} functions {{inDegrees}}, {{outDegrees}}, and {{getDegrees}} each > return {{DataSet<Tuple2<K, Long>>}}. Using {{Long}} creates a new heap object > for every serialization and deserialization. The mutable {{Value}} types do > not suffer from this issue when object reuse is enabled. > I lean towards a preference for conciseness in documentation and performance > in examples and APIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)