[eAccelerator-developers] prune_period, ttl, least recently used

[Geoff S. <ge...@ho...>]

I am using 0.9.5rc1

What is the relationship of shared_memory in RAM to disk caching? How 
does eaccelerator decide what to cache in main memory and what to cache 
on disk?

I have read the descriptions of shm_ttl and shm_prune_period but I don't 
understand the difference - unless it is that the prune_period only 
deletes enough scripts to allow caching of the scripts needing to be 
cached.

Also, I don't understand what  "previous try" means in the documentation 
for "prune_period":  /it tries to remove old scripts if the previous try 
was made more then "shm_prune_period" seconds ago/

I am used to the Least Recently Used algorithm: Whenever the shared 
memory runs out, it would delete the scripts that had been least 
recently used.

I'm looking for a suggestion on how to do this because I don't want to 
give eaccelerator as much ram as it can use.

Geoff