tag:blogger.com,1999:blog-12753102.post5558066941655125077..comments2024-03-28T15:41:37.170-04:00Comments on Ben's Journal: Measuring Linux Memory AllocationBen Simonhttp://www.blogger.com/profile/09833753747177544979noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-12753102.post-1552540521131796032008-10-30T09:42:00.000-04:002008-10-30T09:42:00.000-04:00"just I think it is near impossible to determine w..."just I think it is near impossible to determine what is going on."<BR/><BR/>So well put! <BR/><BR/>I'm also starting to appreciate vmstat more, specifically watching the io wait time.<BR/><BR/>What I really need to do is just install all my apps on a server with like 16GB of ram, and forget about it.ASLdeafinedhttps://www.blogger.com/profile/14224593523488304842noreply@blogger.comtag:blogger.com,1999:blog-12753102.post-19793540744213805422008-10-28T10:30:00.000-04:002008-10-28T10:30:00.000-04:00ah the joys of linux memory... try on a mac... I t...ah the joys of linux memory... try on a mac... I think apple has taken the idea of memory confusion and taken it to a new level... i'm not saying that the memory management is better or worse on mac, just I think it is near impossible to determine what is going on. <BR/><BR/>anyways I'll have to remember <I>pmap</I> next time I run into serious memory errors. Also if the error is in 'your' code, see if <I>valgrind</I> is available. It will help you find memory leaks.NickChttps://www.blogger.com/profile/03247600634502111298noreply@blogger.com