Use less space for UID and Revision
Closed, ResolvedPublic


We currently have uuid and revision stored as strings, which uses a lot more space than we'd need.

As a first optimization we could use the binary representation which would require 16bytes for the uuid and 8 bytes for the 64bit revision.

Secondly we could use a separate table for the uid lookup, and only use the revision in the primary storage, which would allow us to use integer keys.

cmollekopf moved this task from Backlog to Enhancements on the Sink board.Nov 1 2016, 8:42 PM
cmollekopf reassigned this task from cmollekopf to rnicole.May 22 2018, 12:25 PM

Binary UID is in, revision separation is WIP.

cmollekopf closed this task as Resolved.Aug 26 2018, 8:17 PM