5 ms·
We do this all the time. Our tests run against SQLite (I use Mariadb in prod). Each parallel testrun gets its own path in /dev/shm/xx so everything is in ram a
by tarjei 6y ago
We do this all the time. Our tests run against SQLite (I use Mariadb in prod).
Each parallel testrun gets its own path in /dev/shm/xx so everything is in ram as well.
- ptx 6y agoIf you're using SQLite, why the indirection of an in-memory filesystem rather than SQLite's in-memory database feature?
- yencabulator 6y agoNot the person you're asking this, but N connections to sqlite :memory: backend results in N separate database instances. This can be worked around in some scenarios, but not always & reliably. Most importantly, you can't reach the same in-memory database from multiple processes. https://www.sqlite.org/inmemorydb.html https://www.sqlite.org/inmemorydb.html