Maybe run with memory profiling on, so we know what's using up all the memory?
On 14 November 2016 at 03:52, Adrian Tritschler <[email protected] > wrote: > Twice in the last week my camlistore has been killed by the OOM killer. > I've got 16G of RAM on my home desktop linux box, I'm running a script to > ingest some old system backups (from 2010) from a USB drive into > camlistore. The camlistored process typically ends up using up around 40% > of the memory, but twice it's been killed: > > Nov 14 12:49:08 xyz kernel: [157595.386666] Out of memory: Kill process > 15372 (camlistored) score 332 or sacrifice child > Nov 14 12:49:08 xyz kernel: [157595.386740] Killed process 15372 > (camlistored) total-vm:14142340kB, anon-rss:10239996kB, file-rss:4676kB, > shmem-rss:0kB > Nov 14 12:49:08 xyz kernel: [157596.039684] oom_reaper: reaped process > 15372 (camlistored), now anon-rss:0kB, file-rss:44kB, shmem-rss:0kB > > Any suggestions on cutting down the memory usage? > > Adrian > > -- > You received this message because you are subscribed to the Google Groups > "Camlistore" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
