beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-3060) Add performance tests for commonly used file-based I/O PTransforms
Date Wed, 14 Mar 2018 12:13:00 GMT


ASF GitHub Bot logged work on BEAM-3060:

                Author: ASF GitHub Bot
            Created on: 14/Mar/18 12:12
            Start Date: 14/Mar/18 12:12
    Worklog Time Spent: 10m 
      Work Description: szewi commented on issue #4861: [BEAM-3060] Jenkins configuration
allowing to run FilebasedIO tests on HDFS.
   Run Seed Job

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 80304)
    Time Spent: 0.5h  (was: 20m)

> Add performance tests for commonly used file-based I/O PTransforms
> ------------------------------------------------------------------
>                 Key: BEAM-3060
>                 URL:
>             Project: Beam
>          Issue Type: Test
>          Components: sdk-java-core
>            Reporter: Chamikara Jayalath
>            Assignee: Szymon Nieradka
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
> We recently added a performance testing framework [1] that can be used to do following.
> (1) Execute Beam tests using PerfkitBenchmarker
> (2) Manage Kubernetes-based deployments of data stores.
> (3) Easily publish benchmark results. 
> I think it will be useful to add performance tests for commonly used file-based I/O PTransforms
using this framework. I suggest looking into following formats initially.
> (1) AvroIO
> (2) TextIO
> (3) Compressed text using TextIO
> (4) TFRecordIO
> It should be possibly to run these tests for various Beam runners (Direct, Dataflow,
Flink, Spark, etc.) and file-systems (GCS, local, HDFS, etc.) easily.
> In the initial version, tests can be made manually triggerable for PRs through Jenkins.
Later, we could make some of these tests run periodically and publish benchmark results (to
BigQuery) through PerfkitBenchmarker.
> [1]

This message was sent by Atlassian JIRA

View raw message