Re: Machine unresponsive with cache_lock: blocked on... message

[elekktretterr@xxxxxxxxxxxxxx]

>     If that much is constantly swapped out (and swapcache isn't being
>     used) then the run-time footprint is larger then the 3G of ram the
>     32bit kernel can use.


I turned off postgres on the box, and at that moment all the used swap
memory and about 500MB from active memory was cleared. Which raises a
question: why is HAMMER using so much memory, causing applications like
postgres to use swap (and thus run slow). The box has over 3GB of usable
RAM, this should be well enough. I suppose HAMMER is caching the
postgresql ondisk data? Should it cache it? FBSD+UFS2 with the same
postgres dataset uses way less memory.

My other box which runs DF with HAMMER has pretty normal memory usage but
it doesnt run any database software.

Petr