3 ms·
What kind of memory usage are you talking about? That sounds wild. Are you keeping the entire database in memory, or are you flushing to disk? It seems wild t
by echelon 1y ago
What kind of memory usage are you talking about? That sounds wild.
Are you keeping the entire database in memory, or are you flushing to disk?
It seems wild that such a critical and pervasive piece of software would behave like that.
- Leherenn 1y agoKeeping it in memory. After a few days, the memory usage reported by the Activity Monitor (so not the actual resident memory, but the one customers see and complain about) grows from maybe a few 10s MB to a few hundreds MBs. But as far as I can tell, it's more an OS issue than really a Sqlite issue, simply doing malloc/free in a loop results in a similar behaviour. And Sqlite does a lot of allocations. We see a similar problem on Windows, but not as pronounced, and there we can force the OS to reclaim memory. It's probably solvable by using a custom allocator, but at this point it's no longer plug and play the way the GP meant.