On Sun, Mar 21, 2010 at 12:14:11PM -0700, Matthew Dillon wrote: > > :> Try setting it to 40 (it defaults to 23). The max value is 64 > :> which will effectively put all non-memory-mapped file data on the > :> inactive queue, including any data which is repeatedly accessed. > : > :Done. I raised it previously to 30 (I think) and still had a crash. > > It wouldn't effect the crash condition, which was a low memory > condition generated by cache+free followed by a deadlock. The > cycle point only effects active vs inactive. > > But raising the cycle point should reduce the degree by which > active program memory is swapped out. On the flip-side, the > cost of doing this is that file data may be thrown out too quickly. > That is, cacheable file data will be mixed in with uncacheable > file data in the inactive queue and we'll be throwing the baby out > with the dishwater, so to speak. > > I'd like to know if this solves your particular problem (the paging > issue, not the crashing issue), and if so I will change the default > cycle point for the release. So play with it.
We'll see. For now, there's a rsync backup running and the paging activity seems to get more intense: Memory: 473M Active, 1038M Inact, 441M Wired, 46M Cache, 199M Buf, 3380K Free Swap: 4096M Total, 149M Used, 3947M Free, 3% Inuse, 4336K Out -- Francois Tigeot
