An uncompressed table in the binary can be demand paged when needed instead of dirtying pages. Yes, the binary will be bigger meaning that more IO will incur w

An uncompressed table in the binary can be demand paged when needed instead of dirtying pages. Yes, the binary will be bigger meaning that more IO will incur when deploying the application e.g. in docker/k8s. What that extra IO is surely an annoying thing, I'm not sure I'd trade that off for a huge increase in heap allocation right before getting a stacktrace. Since we're talking about containers, it's not uncommon for containers to be configured with tight memory limits and having an OOM during that process could mask the real reason for a panic. Would it be possible to have a more succinct data structure or even directly index the compressed table without having to decompress the whole thing?