-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hash function performance #22
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've built community ID support into VAST to allow for pivoting between ingested PCAPs, Suricata, Zeek, and NetFlow/IPFIX. Our C++ implementation of community ID computation is available here.
We have observed approximately 8% loss in IPFIX ingestion performance when enabling community ID computation.
Recently we have experimented with replacing SHA1 in the community ID computation, and have had great results using xxHash. The overall performance loss went down from 8% to 3%.
I am proposing to use XXH3 (supposed to be stabilized in H1 2020) for community ID v2 to improve the usability on high-throughput paths.
The text was updated successfully, but these errors were encountered: