tfjs-webgpu: Improved timing in benchmarks.

[annxingyuan]

Changes:

• Add disposeAfterEachTrial argument to toggle whether we tidy after each trial
• Make endTrial async so we account for read times in profile
• Change reps default to 1 for fairer comparison against WebGL
• Add new binary op benchmark

To see the logs from the Cloud Build CI, please join either our discussion or announcement mailing list.

---

This change is 

[nsthorat]

Reviewed 1 of 1 files at r1.
Reviewable status: complete! 1 of 1 approvals obtained (waiting on @annxingyuan, @dsmilkov, and @nsthorat)

---

tfjs-webgpu/src/benchmark_ops_test.ts, line 118 at r1 (raw file):

  // tslint:disable-next-line:ban
  xit('add', async () => {

remove the xits?

[annxingyuan]

Reviewable status: complete! 1 of 1 approvals obtained (waiting on @dsmilkov and @nsthorat)

---

tfjs-webgpu/src/benchmark_ops_test.ts, line 118 at r1 (raw file):

Previously, nsthorat (Nikhil Thorat) wrote…

remove the xits?

I think we don't want them to run as part of the default test suite - is there a better way to exclude?

[nsthorat]

Reviewable status: complete! 1 of 1 approvals obtained (waiting on @annxingyuan and @dsmilkov)

---

tfjs-webgpu/src/benchmark_ops_test.ts, line 118 at r1 (raw file):

Previously, annxingyuan (Ann Yuan) wrote…

I think we don't want them to run as part of the default test suite - is there a better way to exclude?

can you exclude them in the karma config?

[annxingyuan]

Reviewable status: complete! 1 of 1 approvals obtained (waiting on @dsmilkov)

---

tfjs-webgpu/src/benchmark_ops_test.ts, line 118 at r1 (raw file):

Previously, nsthorat (Nikhil Thorat) wrote…

can you exclude them in the karma config?

Done