Re:Updating the Git protocol for SHA-256
by richbradshaw on Saturday June 20, 2020 @04:31AM
(#23582629)
If you store them as strings instead of binary (which I'm guessing 99% of hashes are), they take up more DB space currently, and passing them round is slower, e.g. as etags etc.
[ Parent
| on HN ]
Re:Updating the Git protocol for SHA-256
by speedgoose on Saturday June 20, 2020 @04:39AM
(#23582658)
I would guess that once compressed, binary represented as hex strings don't take much more space than base64 strings. Probably still a bit more than the compressed binary though.
Re:Updating the Git protocol for SHA-256
by dependenttypes on Saturday June 20, 2020 @05:57AM
(#23582965)
You won't gain anything by compressing (binary) hashes.
Re:Updating the Git protocol for SHA-256
by speedgoose on Saturday June 20, 2020 @07:07AM
(#23583246)
Oh yes indeed.
Re:Updating the Git protocol for SHA-256
by Dylan16807 on Saturday June 20, 2020 @04:42AM
(#23582665)
This is about printing, not storage.