Don't try to allocate memory until there is only x% free

re: Don't try to allocate memory until there is only x% free

Kirill — Mon, 23 Jan 2012 12:51:34 GMT

As long as my program is "Program 10", I don't see what the problem is...

*trollface*

re: Don't try to allocate memory until there is only x% free

Hear — Sat, 21 Jan 2012 20:10:49 GMT

It reminds me of a time I couldn't hear what someone was saying, so I came closer and told him to repeat, so he spoke again, but more silently (since I was closer).

I couldn't hear him again, so I got even closer... (guess what he did)

re: Don't try to allocate memory until there is only x% free

640k — Sat, 21 Jan 2012 10:53:22 GMT

2 refrigerators is enough for everyone.

re: Don't try to allocate memory until there is only x% free

user — Fri, 20 Jan 2012 17:13:39 GMT

I hope IE guys read your blog.

As I'm writing this there ar three iexplorer processes on my machine consuming 48, 7 and 32 mb of memory for keeping 4 tabs open, 3 from your weblog and one for that amazon thing, let's close that amazon tab ... hmm the first process releases 4mb of memory, let's close a tab from your weblog ... another 8 mb released. now IE is consuming almost 75 mb of memory just to display two pages of your blog.

re: Don't try to allocate memory until there is only x% free

SheepNine — Fri, 20 Jan 2012 15:30:27 GMT

Is it mere coincidence that it is the BLUE process whimpering fetally in the corner while the PINK process proceeds to consume huge swaths of available RAM?

re: Don't try to allocate memory until there is only x% free

Danny — Fri, 20 Jan 2012 10:50:59 GMT

Ray, isn't this just another variation of walls and ladders game with a twist?

re: Don't try to allocate memory until there is only x% free

lefty — Thu, 19 Jan 2012 21:46:15 GMT

Clearly the solution to this problem is to set your memory threshold level at something like 5% so you end up shutting out both Program A and Program B. As the author of Program C, I sure don't care about their performance.

And the solution to Raymond's 'too much food' problem is to send the in-laws to my place. I love free food (maybe not fish eyes, though).

re: Don't try to allocate memory until there is only x% free

Skyborne — Thu, 19 Jan 2012 15:46:57 GMT

> swapping to a local file

And by that I actually mean a "private" file, but that brings up another point: what if your cache is accidentally on a network filesystem?

re: Don't try to allocate memory until there is only x% free

Skyborne — Thu, 19 Jan 2012 15:44:26 GMT

@Ken Hagan, I was thinking along those same lines, but it seems like Program 20 wants *discard* under pressure to implement a weak cache (and probably some strong->weak cache management in-app so that the entire cache doesn't drop and cause thrashing as it gets re-populated and immediately re-dropped under continuing pressure), but everything I know of (esp. on linux) creates *swap* under pressure behavior.

mmap is actually worse, because you get swapping to a local file, maybe on volume manager / encryption / software raid / an ssd that the user doesn't actually want you swapping your cache to all the time.

re: Don't try to allocate memory until there is only x% free

Larry Hosken — Thu, 19 Jan 2012 15:11:37 GMT

cheong00's onto something. When your in-laws leave, you might want to hold an Iron Chef contest/potluck party. Early on some Saturday, you divvy up the left-behind food amongst some friends. That evening, they need to bring back dishes they cooked that incorporates that food. Then comes a dinner party/contest judging.

Heck, maybe don't wait until the in-laws leave. They probably bring food that they like to cook with. They might do well in the contest and thus feel happy.