You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2017/08/24 09:19:00 UTC
[jira] [Updated] (BEAM-160) Port 'NexMark Queries' to Beam for use
as integration test
[ https://issues.apache.org/jira/browse/BEAM-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismaël Mejía updated BEAM-160:
------------------------------
Fix Version/s: 2.2.0
> Port 'NexMark Queries' to Beam for use as integration test
> ----------------------------------------------------------
>
> Key: BEAM-160
> URL: https://issues.apache.org/jira/browse/BEAM-160
> Project: Beam
> Issue Type: Test
> Components: testing
> Reporter: Mark Shields
> Assignee: Etienne Chauchot
> Fix For: 2.2.0
>
>
> A while back we implemented the 'queries' from
> http://datalab.cs.pdx.edu/niagara/NEXMark/
> as Gooogle Dataflow pipelines. We found them useful
> for uncovering performance problems with the sdk, our runners,
> and our service. Many of those problems only manifested under
> high load, multi-day runs, or with high 'backlog' on the incoming
> pub/sub subscriptions.
> We thus think they would be useful for other runners.
> Disclaimer: Though the original 'queries' were proposed as a way to
> benchmark 'continuous SQL' implementations, we have so far only
> used them for internal A/B and regression testing and have not validated
> them as representative of customer workloads. We would thus discourage their use for competitive benchmarks without more work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)