enkiTS VS dflat

If you're open to using a task scheduler library, and want something lighter weight than the alternatives, my permissively licensed C and C++ Task Scheduler for creating parallel programs enkiTS would be a good fit for this.

Rather than a new background thread I would use a task/job system such as my own open source enki Task Scheduler (enkiTS).

As always the multithreading for this is achieved using my permissively licensed C and C++ Task Scheduler for creating parallel programs, enkiTS.

What tasking system are you using? If you're having problems with it you might want to try my enkiTS.

enkiTS: A C and C++ Task Scheduler for creating parallel programs\ (15 comments)

GL_MAP_PERSISTENT_BIT for any data which is changed per-frame, such as constant buffers, particle data, SSBO data etc. This allows the data to be written in parallel (I use my tasking system enkiTS).

This is really, IMHO (as someone implements things on top of SQLite too https://dflat.io) pushes SQLite too far as the implementation of cross-db transactions have some big issues: https://www.sqlite.org/limits.html (the number of attached databases cannot exceed 10 or 125 (if you compile your own)) https://www.sqlite.org/wal.html (in WAL mode, there is no transactional guarantee for cross database transactions (atomic per database, but not cross database))

Dflat: SQLite FlatBuffers\ (4 comments)

Flatbuffers would be better as it doesn't need to deserialize at all (I think protobuf supports to partially deserialization nowadays?). I did something similar with https://dflat.io/ too!