Recommended setup with large cache memory

[Brad Knowles]

At 11:59 AM +0200 2005-09-09, Attila Nagy wrote:

>  It seems that it works, at least the memory usage doesn't grow besides a
>  limit and the cache still operates.

	You should take a look at the internal operations of the program, 
and see what it is really doing inside.  If you did that, I imagine 
that you would not like the results.

>  - dropping the old, unused, etc entried dynamically, to make space for
>  the new ones

	How do you know where they are?  How can you make sure that you 
drop just the old expired entries, if you have no time to search the 
in-memory database to find them and expire them?

>  If the first is the case, I don't know why should I use cleaning-interval.
>  If the second, I guess even a very simple random drop  would be better.

	I am not at all convinced that a simple random drop of any record 
would actually be a better solution.

>  I guess it would be much better to leave cleaning out of the picture. :)
>  BTW, I have a load balancer in front of the caches, but it's still
>  annoying that I need to do a regular cleaning.

	You have to take a shower or a bath every so often, right?  Even 
if there are multiple people in your office that can do your job, 
even you can only go so long before you have to get clean, right?

	Why should you expect that this is any different for computer programs?

-- 
Brad Knowles, <brad at stop.mail-abuse.org>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

     -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
     Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See <http://www.sage.org/> for more info.