Hi Greg!
The idea is very good, especially having these pre-built performance tests
for release testing.
In your opinion, are the tests going to be self-contained, or will they
need a cluster (YARN, Mesos, Docker, etc.)
to bring up a Flink cluster and run things?
Greetings,
Stephan
On Sat,
Hello,
I think that creating a macro-benchmarking module would be a very good
idea. It would make doing performance-related changes much easier and
safer.
I have also used Peel, and can confirm that it would be a good fit for
this task.
> I've also been looking recently at some of the hot code a
Hi Greg,
I just pushed v1.0.0-rc2 for Peel to Sonatype.
As Till said, we are using the framework extensively at the TU for
benchmarking and comparing different systems (mostly Flink and Spark).
We recently used Peel to conduct some experiments for FLINK-2237. If you
want to learn more about the
Hi Greg,
I like the idea to have a macro-benchmarking suite to exactly test the
points you've mentioned. If we don't have reliable performance numbers,
then it will always be hard to tell whether an improvement makes sense or
not (performance-wise).
I think we already undertook a first attempt to
I'd like to discuss the creation of a macro-benchmarking module for Flink.
This could be run during pre-release testing to detect performance
regressions and during development when refactoring or performance tuning
code on the hot path.
Many users have published benchmarks and the Flink libraries
