12 ms·
Because we were not using any numerical properties of the hash. We were not adding it to other hashes, seeing if it was greater than or less than other hashes,
by zomglings 6y ago
Because we were not using any numerical properties of the hash. We were not adding it to other hashes, seeing if it was greater than or less than other hashes, etc.
Literally the only thing we were doing was passing it between shell commands, helm charts, Kubernetes deployments and then back (if we needed to debug).
It sounds like you have a more attractive alternative in this case than to treat hashes as strings. Would love to hear it.
- BlueTemplar 6y agoIn the same thread : https://news.ycombinator.com/item?id=26679590 https://news.ycombinator.com/item?id=26679590 Concise encoding seems to have an hex-int type ?
- zomglings 6y agoProblem is that we were using Kubernetes + helm, which means that we were bound to whatever configuration language they use.
- BlueTemplar 6y agoSo the fault is on them.