GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/2779

    [FLINK-5046] [tdd] Preserialize TaskDeploymentDescriptor information

    In order to speed up the serialization of the TaskDeploymentDescriptor we 
can pre serialize
    all information which stays the same for all TaskDeploymentDescriptors. The 
information which
    is static for a TDD is the job related information contained in the 
ExecutionGraph and the
    operator/task related information stored in the ExecutionJobVertex.
    
    In order to pre serialize this information, this PR introduces the 
JobInformation class
    and the TaskInformation class which are stored in serialized form in the 
ExecutionGraph
    and the ExecutionJobVertex, respectively.

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

    $ git pull https://github.com/tillrohrmann/flink 
eagerStreamConfigSerialization

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

    https://github.com/apache/flink/pull/2779.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 #2779
    
----
commit fb7621a5a5023595a89d7e92562b503ec2a039e5
Author: Till Rohrmann <trohrm...@apache.org>
Date:   2016-11-09T18:11:36Z

    [FLINK-5046] [tdd] Preserialize TaskDeploymentDescriptor information
    
    In order to speed up the serialization of the TaskDeploymentDescriptor we 
can pre serialize
    all information which stays the same for all TaskDeploymentDescriptors. The 
information which
    is static for a TDD is the job related information contained in the 
ExecutionGraph and the
    operator/task related information stored in the ExecutionJobVertex.
    
    In order to pre serialize this information, this PR introduces the 
JobInformation class
    and the TaskInformration class which are stored in serialized form in the 
ExecutionGraph
    and the ExecutionJobVertex, respectively.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to