On Tue, Nov 28, 2000 at 01:05:58PM +0200, Igor Khasilev wrote: > On Tue, 28 Nov 2000, Peter Gervai wrote: > > # config file: > > mem_max 16m > > lo_mark 8m > > > > # ps awux: > > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > > proxy 3314 0.1 22.9 62780 29408 ? S Nov22 8:24 /usr/sbin/oops -c >/etc/oops/oops.cfg [...] > If you are under silaris, I can advize to use ptmalloc. If you are under > Linux, ptmalloc is already there. I'm using Debian Linux (not too old one). Do I have anything to do about this? I don't know about using mallocs, I suppose oops automagically use ptmalloc then (is there any way to check which malloc do oops use?) RSS is the actual resident size (29M), so I suppose it contains 16M data cache and 13M structures? Isn't this a bit big? Oops now uses 3 storages, 20+100+600MB, this is not that much I think. > VSZ sometimes can not move down even if you free almost all allocated > memory. ptmalloc handle this situation better then some other mallocs, it > can return unused memory to system. The most important thing is that vsz > must stop at some moment. I'll watch it closely. What I worry about is always when the VSZ gets swapped... and gets used from there. It seems good, as the swapped out data doesn't seem to get used much. So far. > > (Is there a point to make a stat about memory allocation?) > > I just don't know how to do this in portable way. The only way on my lazy mind is a malloc debugger, there are probably several ones floating around the net. Those wrap malloc() calls and record allocations is some tables. (Some out of my debian/linux catalog: electric-fence [it's rather a helper for bad alloc's], ccmalloc, dmalloc [some stats, too], debauch) It shall not be used for normal use (it slows down memory allocations, though I don't know the amount of the impact. Probably most of these tools are pretty portable - some maybe don't. I am not an active C developer, cannot say preferences.... But it can be a debug aid, IF required. I don't think it's such a big problem now, so it doesn't really worth the work unless there is a problem requiring this solution. :-) ===================================================================== If you would like to unsubscribe from this list send message to [EMAIL PROTECTED] with "unsubscribe oops-eng" in message body. Archive is accessible on http://www.paco.net/oops/
