The @aws-crypto/crc32 is 5x slower than the fastest implementation in Node.js and >20x slower in browser

[trivikr]

Is your request related to a problem? Please describe.

Refs: https://github.com/trivikr/benchmark-crc32

Benchmarks in Node.js v16.4.0:

crc x 418,858 ops/sec ±0.33% (91 runs sampled)
crc-32 x 426,337 ops/sec ±0.25% (96 runs sampled)
buffer-crc32 x 318,404 ops/sec ±0.33% (94 runs sampled)
@aws-crypto/crc32 x 74,763 ops/sec ±0.90% (95 runs sampled)
Fastest is crc-32

Benchmarks in Firefox browser v78.10.1esr:

crc x 188,843 ops/sec ±0.48% (63 runs sampled)
crc-32 x 370,060 ops/sec ±0.85% (67 runs sampled)
buffer-crc32 x 80,874 ops/sec ±2.67% (64 runs sampled)
@aws-crypto/crc32 x 15,069 ops/sec ±1.78% (64 runs sampled)
Fastest is crc-32

Describe the solution you'd like

The @aws-crypto/crc32 implementation to be at par or close to other CRC32 implementations.