[
https://issues.apache.org/jira/browse/BEAM-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Pilloud updated BEAM-10643:
----------------------------------
Description:
The perfkit dashboard was just turned down, it had a page comparing different
implementations for the same query for each runner (Dataflow, Direct, ect). For
example, this would be "Java Batch vs Java Streaming vs SQL vs ZetaSQL on
Dataflow".
The new grafina dashboard breaks down nexmark per engine (Java, SQL, missing
ZetaSQL), which isn't a useful comparison as different runners have different
sample sizes and measurement techniques.
was:
The perfkit dashboard was just turned down, it had a page comparing different
implementations for the same query for each runner (Dataflow, Direct, ect). For
example, this would be "Java vs SQL vs ZetaSQL on Dataflow".
The new grafina dashboard breaks down nexmark per engine (Java, SQL, missing
ZetaSQL), which isn't a useful comparison as different runners have different
sample sizes and measurement techniques.
> Grafina dashboard missing per runner nexmark pages
> --------------------------------------------------
>
> Key: BEAM-10643
> URL: https://issues.apache.org/jira/browse/BEAM-10643
> Project: Beam
> Issue Type: Bug
> Components: testing-nexmark
> Reporter: Andrew Pilloud
> Assignee: Kamil Wasilewski
> Priority: P2
>
> The perfkit dashboard was just turned down, it had a page comparing different
> implementations for the same query for each runner (Dataflow, Direct, ect).
> For example, this would be "Java Batch vs Java Streaming vs SQL vs ZetaSQL on
> Dataflow".
> The new grafina dashboard breaks down nexmark per engine (Java, SQL, missing
> ZetaSQL), which isn't a useful comparison as different runners have different
> sample sizes and measurement techniques.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
