elastic / elastic/logstash

Fix redundant byte[] allocation when computing CRC32

Open
#7,111 4 comments 0 reactions 0 assignees View on GitHub
performance improvements v5.5.0 v6.0.0
Dominant language
Java
Stars
14.9k
Forks
3.5k
Avg merge
19h 14m
Merged PRs (30d)
63

Description

As pointed out in #7058 and specifically https://github.com/elastic/logstash/pull/7058#issuecomment-301588948

there are more cases than just this one that have redundant `byte[]` allocation for CRC32.
Those should be fixed the same way they were fixed in that PR and the logic dried up across CRC32 computations.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.