zson

jsonb doesn't do key interning as far as I know. Every field name will be repeated in every record vs a normal column which will only have the column name once in the db. This really adds up on a large database. Mongo used to recommend short key names and I even think some client would translate them based on some definition to try and save disk/memory/io https://github.com/postgrespro/zson tries to do key compression. Also its not that Linq can't do what you want, its that if you do certain things that can't be translated to SQL the whole intermediate result will be retrieved from the db, deserialized then the linq statement will be run in memory on the client. Its like putting ToList in the middle of your linq statement where a maybe a few million rows might need to be processed to give the very small result. If the linq statement was b

There is a comparison table at the end of the project's README (https://github.com/afiskon/zson). However, the table columns are not explained very well. It is not 100% clear to me whether "before" means "uncompressed" or "PGLZ compressed". Compression ratio could be different depending on documents, database schema, number of rows, etc. But in general ZSON compression is much better than build-in PostgreSQL compression (PGLZ): before | after | ratio ------------+------------+------------------ 3961880576 | 1638834176 | 0.41365057440843 (1 row) before | after | ratio ------------+------------+------------------- 8058904576 | 4916436992 | 0.610062688500061 (1 row) before | after | ratio -------------+------------+-------------------