3 ms·
255 bytes is obviously overkill for a key (a 32 or 64 byte secure hash of anything larger than 255 bytes can be assumed to unique), so it's just a question of w
by aidenn0 6y ago
255 bytes is obviously overkill for a key (a 32 or 64 byte secure hash of anything larger than 255 bytes can be assumed to unique), so it's just a question of what values are usefully in 255 bytes:
One thought that comes to mind is a distributed store with centralized master, 255 bytes is plenty for a hostname and resource ID.
- cperciva 6y ago255 bytes is obviously overkill for a key If they're hashes, sure. If you want to answer range requests -- e.g. "give me everything starting with ABCDEF" -- you may have a less densely utilized address space (rather like IP networking has had). My accounting database has keys of the form "usage/"<256-bit user ID><20-byte timestamp><64-bit machine ID><usage type string>. Not 255 bytes, to be sure, but not trivially short either.