what we could do is that the secondlevelcache sets the max page versions to 1 So that a page keeps 1 max page versions besides the current one. Then one back button (that is the case for 90% of the time i guess) is done in mem And the overhead is only 1 changeset per page thats in mem and on disk..
johan On 1/9/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 1/9/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > you can have the the versions to MAX but this still will not result in > a session filling up because you still have the max pages, But that is i > guess > not used anymore in the SeconLevelCache. Because we don't use the > EvictPageStrategy > anymore. Even the old way, you can have one page with 1000 changes on it, each of the changes eating some memory. Eelco
