Turbopack: use xxhash3_128 for content hashes (#90583)
Move to 128 bit hashes, so that we can include the untruncated hashes in the manifest in #88607
If anything, this is faster, surprisingly:
```
upgrade twox-hash 448a36b449
pnpm next build --experimental-build-mode=compile 430.13s user, 73.72s system, 724% cpu, 1:09.53 total
pnpm next build --experimental-build-mode=compile 430.05s user, 82.51s system, 736% cpu, 1:09.56 total
pnpm next build --experimental-build-mode=compile 419.95s user, 89.50s system, 697% cpu, 1:13.03 total
pnpm next build --experimental-build-mode=compile 425.95s user, 75.87s system, 748% cpu, 1:07.00 total
use Xxh3Hash128Hex for content hashes ffd6a87f09
pnpm next build --experimental-build-mode=compile 397.42s user, 53.18s system, 670% cpu, 1:07.25 total
pnpm next build --experimental-build-mode=compile 416.68s user, 66.32s system, 762% cpu, 1:03.32 total
pnpm next build --experimental-build-mode=compile 412.63s user, 68.30s system, 774% cpu, 1:02.12 total
pnpm next build --experimental-build-mode=compile 419.09s user, 68.57s system, 756% cpu, 1:04.50 total
```
https://github.com/Cyan4973/xxHash says:
| Hash Name | Width | Bandwidth (GB/s) | Small Data Velocity | Quality | Comment |
| --------- | ----- | ---------------- | ----- | --- | --- |
| __XXH3__ (SSE2) | 64 | 31.5 GB/s | 133.1 | 10
| __XXH128__ (SSE2) | 128 | 29.6 GB/s | 118.1 | 10
| __XXH64__ | 64 | 19.4 GB/s | 71.0 | 10
| __XXH32__ | 32 | 9.7 GB/s | 71.9 | 10
Showing
File moved
File moved
File moved
File moved
File moved
File moved
File moved
Please
register
or
sign in
to comment