[BEAM-3060] split one job into several jobs, one for each IO.

[DariuszAniszewski]

Follow this checklist to help us incorporate your contribution quickly and easily:

• Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

---

[DariuszAniszewski]

Run seed job

[DariuszAniszewski]

Run Java TextIO Performance Test

[DariuszAniszewski]

@chamikaramj For this PR to properly run, following tables must be created in BigQuery:

beam_performance.textioit_pkb_results
beam_performance.compressed_textioit_pkb_results
beam_performance.avroioit_pkb_results
beam_performance.tfrecordioit_pkb_results

or this PR on PerfKit that allows automatic creation must be merged.

[DariuszAniszewski]

Run seed job

[DariuszAniszewski]

Run Java TextIO Performance Test

[DariuszAniszewski]

Run Java AvroIO Performance Test

[DariuszAniszewski]

Run Java TextIO Performance Test

[DariuszAniszewski]

Run Java CompressedTextIO Performance Test

[DariuszAniszewski]

Run Java TFRecordIO Performance Test

[DariuszAniszewski]

@chamikaramj Alan created tables and as you can see above tests are now passing. Each IO has own Jenkins job and pushes data to dedicated BQ table, there will be dedicated dashboard as well.
This PR is ready to review, PTAL
Thanks

[chamikaramj]

LGTM. Thanks.