perf(benchmarks): Migrate remaining benchmark to best

[diervo]

Details

Upgrade the old benchmarks to use best.

[salesforce-best-lwc-internal]

Benchmark comparison

Base commit: a5ad51d | Target commit: ffc2e7d

benchmark	base(a5ad51d)	target(ffc2e7d)	trend
clear-1k.benchmark:benchmark-table/clear/1k	16.14 (± 0.48 ms)	12.46 (± 0.48 ms)	👍
create-1k.benchmark:benchmark-table/create/1k	183.62 (± 1.32 ms)	150.36 (± 1.32 ms)	👍
update-10th-1k.benchmark:benchmark-table/update-10th/1k	145.66 (± 1.23 ms)	123.92 (± 1.23 ms)	👍

[salesforce-best-lwc-internal]

Benchmark comparison

Base commit: a5ad51d | Target commit: 0cb38b9

benchmark	base(a5ad51d)	target(0cb38b9)	trend
clear-1k.benchmark:benchmark-table/clear/1k	16.14 (± 0.80 ms)	15.11 (± 0.80 ms)	👍
create-1k.benchmark:benchmark-table/create/1k	183.62 (± 10.66 ms)	164.38 (± 10.66 ms)	👍
update-10th-1k.benchmark:benchmark-table/update-10th/1k	145.66 (± 2.86 ms)	133.61 (± 2.86 ms)	👍

[diervo]

@pmdartus I'm not happy having two independent benchmarks (benchmark-table and benchmark-table-component) in the same file, because if we were to have a memory leak, or any sort of intrinsic dependency, data will be skewed.

Note that new tests don't show here yet because the diffing is against the common.

I think the recommendation would always be to have independent benchmarks in independent files.

[salesforce-best-lwc-internal]

Benchmark comparison

Base commit: a5ad51d | Target commit: d8d5b59

benchmark	base(a5ad51d)	target(d8d5b59)	trend
clear-1k.benchmark:benchmark-table/clear/1k	16.14 (± 1.44 ms)	37.85 (± 1.44 ms)	👎