This content has been marked as final.
Show 4 replies
-
1. Re: L1 Cache configuration - restricting the number of entries
manik Apr 28, 2010 9:34 AM (in response to srininara)TTL is the only way. But keep in mind that L1 entries are stored in the core data container so if you have enabled eviction and have set maxEntries, this maxEntries number is L1 entries + core entries. So this will limit the size of your cache.
-
2. Re: L1 Cache configuration - restricting the number of entries
srininara Apr 28, 2010 1:47 PM (in response to manik)Thanks Manik for the immediate response. Your answer does clarify the issue I was trying to solve. Thanks a lot again.
Best Regards,
Srini
-
3. Re: L1 Cache configuration - restricting the number of entries
srininara May 5, 2010 8:56 AM (in response to srininara)One additional question: Since the L1 entries and the actual node specific entries use the same container, are they both handled the same way in case of eviction and expiry. Are they given the same status?
-
4. Re: L1 Cache configuration - restricting the number of entries
manik May 5, 2010 9:25 AM (in response to srininara)1 of 1 people found this helpfulYes they are, except that L1 entries automatically get the L1 time to live applied as a lifespan.