[FLINK-3599] GSoC: Code Generation in Serializers

• Type: Improvement
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Component/s: API / Type Serialization System
• Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned gsoc2016 mentor pull-request-available
• Assignee: Unassigned
• Reporter: Márton Balassi
• Created: 10/Mar/16 10:22
• Updated: 19/Feb/22 10:37

Description

The current implementation of the serializers can be a
performance bottleneck in some scenarios. These performance problems were
also reported on the mailing list recently [1].

E.g. the PojoSerializer uses reflection for accessing the fields, which is slow [2].

For the complete proposal see [3].

[1] http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Tuple-performance-and-the-curious-JIT-compiler-td10666.html

[2] https://github.com/apache/flink/blob/master/flink-core/src/main/java/org/apache/flink/api/java/typeutils/runtime/PojoSerializer.java#L369

[3] https://docs.google.com/document/d/1VC8lCeErx9kI5lCMPiUn625PO0rxR-iKlVqtt3hkVnk

Issue Links

• links to: GitHub Pull Request #2211
• links to: GitHub Pull Request #2211

Sub-Tasks

• Code generation for POJO serializer: Open
• Code generation for POJO comparators: Open
• Annotations for code generation: Open