Skip to content

Hash calculation for uber archive entries that require unpacking is inefficient #46202

@wilkinsona

Description

@wilkinsona

See #46183 for background.

There are two inefficiencies:

  • Calculating the hash loads the whole file into memory
  • The whole file is read twice (once for the CRC-32 and once for the SHA-1 hash).

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions