←back to thread

275 points whatisabcdefgh | 1 comments | | HN request time: 0s | source
Show context
liuliu ◴[] No.45133756[source]
One thing I would call out, if you use SQLite as an application format:

BLOB type is limited to 2GiB in size (int32). Depending on your use cases, that might seem high, or not.

People would argue that if you store that much of binary data in a SQLite database, it is not really appropriate. But, application format usually has this requirement to bundle large binary data in one nice file, rather than many files that you need to copy together to make it work.

replies(1): >>45134101 #
Retr0id ◴[] No.45134101[source]
You can split your data up across multiple blobs
replies(3): >>45135219 #>>45136032 #>>45140501 #
1. bob1029 ◴[] No.45136032[source]
This is essential if you want to have encryption/compression + range access at the same time.

I've been using chunk sizes of 128 megabytes for my media archive. This seems to be a reasonable tradeoff between range retrieval delay and per object overhead (e.g. s3 put/get cost).