[JBossCache] - Re: Passivation false?
by bstansberryï¼ jboss.com
Quick example, showing what state is in RAM and in the persistent store after each step of a 6 step process:
1) Insert /A
2) Insert /B
3) Eviction thread runs, evicts /A
4) Read /A
5) Eviction thread runs, evicts /B
6) Remove /B
Passivation=false
1) RAM: /A Disk: /A
2) RAM: /A, /B Disk: /A, /B
3) RAM: /B Disk: /A, /B
4) RAM: /A, /B Disk: /A, /B
5) RAM: /A Disk: /A, /B
6) RAM: /A Disk: /A
Passivation=true
1) RAM: /A Disk:
2) RAM: /A, /B Disk:
3) RAM: /B Disk: /A
4) RAM: /A, /B Disk:
5) RAM: /A Disk: /B
6) RAM: /A Disk:
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077555#4077555
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077555
18Â years, 8Â months
[JBossCache] - Re: Passivation false?
by bstansberryï¼ jboss.com
For passivation=false, key sentence in the doc is "Whenever an element is modified, added or removed, then that modification is persisted in the backend store via the cache loader." There's no direct relationship between eviction and cache loading. If you don't use eviction, what's in the persistent store is basically a copy of what's in memory. If you do use eviction, what's in the persistent store is basically a superset of what's in memory (includes nodes that have been evicted).
For passivation=true, there is a direct relationship between eviction and the cache loader. Writes to the persistent store via the cache loader only occur as part of the eviction process. In this case, what's in memory and what's in the persistent store are two subsets of the total information set, with no intersection between the subsets.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077553#4077553
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077553
18Â years, 8Â months