You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2015/02/13 17:07:11 UTC

[jira] [Updated] (FLINK-1541) GSoC project: Distributed profiling

     [ https://issues.apache.org/jira/browse/FLINK-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-1541:
---------------------------------
    Issue Type: New Feature  (was: Improvement)

> GSoC project: Distributed profiling
> -----------------------------------
>
>                 Key: FLINK-1541
>                 URL: https://issues.apache.org/jira/browse/FLINK-1541
>             Project: Flink
>          Issue Type: New Feature
>            Reporter: Till Rohrmann
>            Assignee: Robert Metzger
>            Priority: Minor
>              Labels: distributed, gsoc2015, java, scala
>
> Understanding why a given program behaves in a certain way is often difficult and requires in many cases profiling. The profiling allows to detect hot spots in a program which are worthwhile for further investigation. For non-distributed applications there exists a wide variety of useful tools which achieve exactly that. However, Flink currently lacks the capability to profile distributed jobs.
> Therefore, we would like to set up the infrastructure necessary for distributed profiling. First, this requires a thorough evaluation of existing tools in order to see how they could be used for profiling within Flink. 
> The profiling will most likely comprises the following steps:
> 1. Initiating the system and user code instrumentation
> 2. Collecting the profiling information on the distributed components
> 3. Aggregation of the generated profiling information and a proper visualization



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)