Warning
For testing only! Do not use this without knowing the risks.
Main differences from v2 experimental release:
- batch size reduced from 5000 to 1000 to help keep per transaction memory smaller
- cache size allocation changes -- minimal difference
shrink_memoryusage changes- fixes to folder size and index status updates.
In the stable/beta releases of FileBrowser Quantum, all memory (RAM) is held in application space. A difference you may notice here is that sqlite can sometimes use more memory on docker stats or total os memory statistics like task manager. But here's an explanation for whats going on and what to look for:
Previously, all memory used by the index was critical and held by the application in a way that would OOM if there was not enough RAM available. With sqlite, its possible theres paged memory which can increase but should not cause OOM because its reclaimable by the OS.
Now, its safe and useful to place limits in docker memory if needed -- and this will actually keep memory lower in docker stats because the os will reclaim the paged cache
I also added the option to use the cgo driver if you complie with flag cgosql , but I have it compiled without it because I didn't find any benefit in using the cgo driver when enabling it (which is great!)