Large object wants to eat all memory

Hi,

  sometimes Squid keeps very large objects (larger than maxObjectSize)
  completely in memory until last client finishes downloading.
  I see this on 2.5 and 2.6 pre-commloops. It causes thrashing and
  big performance hit when all RAM is depleted.

  Debugging shows that storeSwapOut is the offending function.
  Bad thing happens when storeSwapOutAble(e) returns true and
  storeCheckCachable(e) returns false (because object is too big).
  In this case mem->inmem_lo stays at 0 and swapout never starts
  (this happens when Content-Length field is present in headers).

:wq
                                        With best regards,
                                           Vladimir Savkin.
Received on Sun Mar 24 2002 - 05:02:21 MST