[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316369#comment-16316369
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user pnowojski closed the pull request at:

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


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: Sub-task
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>  Labels: benchmarks
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316365#comment-16316365
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user NicoK commented on the issue:

https://github.com/apache/flink/pull/5134
  
merged in c816191113d813156467f3e33856636ef0bcce38
@pnowojski can you close this PR?


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: Sub-task
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>  Labels: benchmarks
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289434#comment-16289434
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user StephanEwen commented on the issue:

https://github.com/apache/flink/pull/5134
  
Would be great if someone could check with Apache legal if this is actually 
in line with policies. Either on the `LEGAL` Jira, or on the 
legal-disc...@apache.org mailing list.


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: Sub-task
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>  Labels: benchmarks
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287852#comment-16287852
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user zentol commented on the issue:

https://github.com/apache/flink/pull/5134
  
Skipping the `maven-deploy-plugin` should accomplish that:

```



org.apache.maven.plugins
maven-deploy-plugin

true




```


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287845#comment-16287845
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user StephanEwen commented on the issue:

https://github.com/apache/flink/pull/5134
  
I having a `flink-benchmarks` repo is not a solution that the community 
likes, we could check whether adding it in `test` scope is okay, if we ensure 
we do not publish a "test-jar" - that way there is no redistribution and no 
user could accidentally pull it in.


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287693#comment-16287693
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user greghogan commented on the issue:

https://github.com/apache/flink/pull/5134
  
@StephanEwen thanks for the link and thoughtful discussion. Including `jmh` 
benchmarks has come up multiple times. Do you see any path to including such a 
benchmark module in the main Flink repo?


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283741#comment-16283741
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user StephanEwen commented on the issue:

https://github.com/apache/flink/pull/5134
  
I also think being more on the cautious side is actually a good thing. 
Given how scared and confused many people and companies are with respect to 
open source and accidentally infringement of IP, being cautious is good, in my 
opinion.

There is an interesting comment from Ted Dunning on a related question, 
basically saying that if things could be a problem or not, think if some 
cautious/picky users might perceive them as a problem:

https://lists.apache.org/thread.html/fc3992c13cc30f889c820d1cfd6be61b63a5be4efa7c9101262474c9@%3Clegal-discuss.apache.org%3E


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283734#comment-16283734
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user StephanEwen commented on the issue:

https://github.com/apache/flink/pull/5134
  
@greg I think there is one more requirement by the ASF (not necessarily the 
Apache License itself), which is making sure that downstream consumers of 
Apache projects are always explicitly aware when they are consuming something 
(even when the build themselves) that has friction with the ASL 2.0.

My preferred solution would still be a separate repository. Executing 
benchmarks during tests is pretty tricky anyways, because their result depends 
so much on where the benchmark is executed, and what happens concurrently on 
the machine, is it a VM or container, etc.


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283657#comment-16283657
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user greghogan commented on the issue:

https://github.com/apache/flink/pull/5134
  
@pnowojski see FLINK-2848 and FLINK-2973. Also the BSD + Patents 
conversation along with Flink's dependence on Amazon's Kinesis library 
(likewise [Category X](https://www.apache.org/legal/resolved.html#category-x)). 
I now think we have been overly cautious in this regard, not necessarily a bad 
thing.

As @StephanEwen noted, the GPL-dependent code must be an [optional 
component](https://www.apache.org/legal/resolved.html#optional). We [do 
this](https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/connectors/kinesis.html)
 with Kinesis by not releasing convenience binaries but requiring the user to 
compile from source with an explicit flag. I think we are safe to include a 
`flink-benchmarks` module which is not depended on or included in the Flink 
distribution. The benchmarks are Apache licensed, only the dependence on `jmh` 
prohibits distribution, so can be included in the (source) release. These are 
performance, not integration, tests so would be run manually rather than during 
the build.

I agree with @StephanEwen's caution but we would not be releasing GPL code, 
it is not obvious that `jmh` is GPL licensed, and Java itself is GPL.


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283365#comment-16283365
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user StephanEwen commented on the issue:

https://github.com/apache/flink/pull/5134
  
@greghogan That may or may not be possible, not 100% sure. Re-distributing 
it does certainly not work.

To my current understanding, the Apache guidelines say we would need to 
make sure that downstream consumers of Flink (also the source) don't 
accidentally pull in a GPL license. For weak copyleft, where consuming it only 
via linking, it is okay, but for strong copyleft, where accidentally linking it 
results in copyleft, I think the hurdles for that are pretty high. There are 
some gray zone areas (like MPL) where the understanding is that "optional" 
dependency is okay because it requires an explicit action by a downstream user 
(re-adding the dependency) and the potential damage is not too high.

I have seen a lot of cases first hand in the past months how many companies 
that want to use open source freak out as soon as they see an instance of GPL. 
We would make Flink's adoption easier if we did not have that.

My first suggestion would be to consolidate this in a separate 
`flink-benchmarks` repository. That would also keep the core Flink repository 
"clear" of GPL. I could check with Apache legal for a final answer.


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283309#comment-16283309
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user pnowojski commented on the issue:

https://github.com/apache/flink/pull/5134
  
It seems like `commons-lang` doesn't have any issues with using `jmh` in 
tests: https://commons.apache.org/proper/commons-lang/dependencies.html

However @greghogan do you remember my previous attempt with JMH in Flink? 
https://github.com/apache/flink/pull/4323 Was it a false alarm?


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283159#comment-16283159
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user pnowojski commented on the issue:

https://github.com/apache/flink/pull/5134
  
@zentol putting this code in external repository would make those 
benchmarks very fragile, since they depend on Flink internals. Almost any 
refactor made in Flink's network stack would brake the external repository (of 
which most committers are not even aware of) and would require coordinated 
commits, which would be unmaintainable.

@greghogan hmmm, that's a very tempting option, however I'm not the one 
that must be convinced that such option is legally viable.  


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282687#comment-16282687
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user casidiablo commented on a diff in the pull request:

https://github.com/apache/flink/pull/5134#discussion_r155667757
  
--- Diff: 
flink-runtime/src/test/java/org/apache/flink/runtime/io/network/benchmark/SerializingLongReceiver.java
 ---
@@ -0,0 +1,101 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.flink.runtime.io.network.benchmark;
+
+import org.apache.flink.runtime.io.network.api.reader.MutableRecordReader;
+import org.apache.flink.runtime.io.network.partition.consumer.InputGate;
+import org.apache.flink.runtime.util.EnvironmentInformation;
+import org.apache.flink.types.LongValue;
+
+/**
+ * {@link ReceiverThread} that deserialize incoming messages.
+ */
+public class SerializingLongReceiver extends ReceiverThread {
+
+private long maxLatency = Long.MIN_VALUE;
+private long minLatency = Long.MAX_VALUE;
+private long sumLatency;
+private long sumLatencySquare;
+private int numSamples;
+
+private final MutableRecordReader reader;
+
+public SerializingLongReceiver(InputGate inputGate, int 
expectedRepetitionsOfExpectedRecord) {
+super(expectedRepetitionsOfExpectedRecord);
+this.reader = new MutableRecordReader<>(
+inputGate,
+new String[]{
+EnvironmentInformation.getTemporaryFileDirectory()
+});
+}
+
+protected void readRecords(long lastExpectedRecord) throws Exception {
--- End diff --

Add `@Override`?


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282181#comment-16282181
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user greghogan commented on the issue:

https://github.com/apache/flink/pull/5134
  
Or if `flink-benchmarks` does not need to be distributed then that code 
could be contributed to the main Flink repository.


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282080#comment-16282080
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

Github user zentol commented on the issue:

https://github.com/apache/flink/pull/5134
  
Why do you want to add these to flink when they are only used by an 
external repository? Wouldn't it make sense to consolidate all benchmarking 
code to the flink-benchmark repo?


> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (FLINK-8220) Implement set of network throughput benchmarks in Flink

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLINK-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281998#comment-16281998
 ] 

ASF GitHub Bot commented on FLINK-8220:
---

GitHub user pnowojski opened a pull request:

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

[FLINK-8220] Implement set of network benchmarks

This PR implements sets of network benchmarks that are intended to simulate 
various workloads for network stack. Benchmarks will be executed by 
`flink-benchmarks` project. We want to keep the code of the benchmarks here, 
since components they are using are not part of public api and we don't wont 
them braking unknowingly on changes in the flink code.

## Verifying this change

This change adds two tests ensuring that benchmarks are compiling and 
executing as expected without an exceptions.

## Does this pull request potentially affect one of the following parts:

  - Dependencies (does it add or upgrade a dependency): (yes / **no**)
  - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
  - The serializers: (yes / **no** / don't know)
  - The runtime per-record code paths (performance sensitive): (yes / 
**no** / don't know)
  - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
  - The S3 file system connector: (yes / **no** / don't know)

## Documentation

  - Does this pull request introduce a new feature? (yes / **no**)
  - If yes, how is the feature documented? (**not applicable** / docs / 
JavaDocs / not documented)


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

$ git pull https://github.com/pnowojski/flink network-benchmarks

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

https://github.com/apache/flink/pull/5134.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 #5134


commit 5151d74980fd5995c718173ea03db5049ed0ada2
Author: Piotr Nowojski 
Date:   2017-11-28T15:49:37Z

[FLINK-8172][network] Write to memorySegment directly in RecordSerializer

This increases throughput of network stack by factor of 2, because 
previously
method getMemorySegment() was called twice per record and it is a 
synchronized
method on recycleLock, while RecordSerializer is sole owner of the Buffer at
this point, so synchronisation is not needed.

commit 42a6a0daefdb9e9b1185a8195c28eccf055a83ce
Author: Piotr Nowojski 
Date:   2017-11-28T07:41:40Z

[hotfix][test] Add timeout for joining with CheckedThread

commit b777e4f44344f12d0196c77515aac0815e7f31c5
Author: Piotr Nowojski 
Date:   2017-11-28T07:42:19Z

[hotfix][util] Added suppressExceptions for lambda functions

commit 28e25a2bd0af704af1fa1b084be6b0cfa05d9928
Author: Piotr Nowojski 
Date:   2017-12-07T09:03:32Z

[FLINK-XXX][network-benchmarks] Define network benchmarks in Flink project

commit 4f88c6522e176bc20ae53c67136e53dc7970c9e0
Author: Nico Kruber 
Date:   2017-12-07T09:03:49Z

[FLINK-XXX][network-benchmarks] Define latency network benchmarks in Flink 
project




> Implement set of network throughput benchmarks in Flink
> ---
>
> Key: FLINK-8220
> URL: https://issues.apache.org/jira/browse/FLINK-8220
> Project: Flink
>  Issue Type: New Feature
>  Components: Network
>Reporter: Piotr Nowojski
>Assignee: Piotr Nowojski
>
> Benchmarks should be defined and implemented in flink project and they will 
> be executed in {{flink-benchmarks}} project.
> Configurable parameters: number of record writers and number of channels.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)