Investigate a faster hashing algorithm that JSON stable stringify
See original GitHub issueA quick analysis with a flamegraph shows that safe-stable-stringify
is the major bottleneck for this cache.
We should investigate if we could come up with a faster algorithm for hashing objects but with the same properties.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:9 (8 by maintainers)
Top Results From Across the Web
zkldi/fast-json-stable-hash - GitHub
Fast JSON Stable Hash (pronounced fish) is a fast, stable JSON hashing library. Stable. The algorithm is stable for different orders of keys....
Read more >fast-json-stable-stringify - npm
Start using fast-json-stable-stringify in your project by running `npm i fast-json-stable-stringify`. There are 1259 other projects in the ...
Read more >fast-json-stable-hash - npm Package Health Analysis - Snyk
Fast JSON Stable Hash (pronounced fish) is a fast, stable JSON hashing library. Stable. The algorithm is stable for different orders of keys....
Read more >Hash | npm.io
deterministic JSON.stringify() with custom sorting to get deterministic hashes from stringified results, with no public domain dependencies.
Read more >Which hashing algorithm is best for uniqueness and speed?
I want a hash algorithm designed to be fast, yet remain fairly unique to avoid collisions. algorithms · security · performance · hashing ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It has been updated this week.
another option would be to modify the
serialize()
function so it constructs/returns a string instead of an object that’s later stringified. Not sure if this is feasible though.@mcollina does the following screenshot corroborate your findings?