Difficult to say ... we have disabled page versioning and se dump sessions onto disk every 5 minutes to minimize memory hassles.
But I am no master ;) ** Martin 2011/7/9 richard emberson <richard.ember...@gmail.com>: > This is a question for Wicket masters and those application builders > whose application match the criteria as specified below. > > [In this case, a Wicket master is someone with a knowledge > of how Wicket is being used in a wide spectrum of applications > so that they have a feel for what use-cases exist in the real world.] > > Wicket is used in a wide range of applications with a variety of > usage patterns. What I am interested in are those applications where > an appreciable number of the pages in memory are pages that had > previously been serialized and stored to disk and then reanimated, > not found in an in-memory cache and had to be read from disk and > de-serialized back into an in-memory page; which is to say, > applications with an appreciable number of reanimated pages. > > Firstly, do such applications exists? These are real-world > applications where a significant number of pages in-memory > are reanimated pages. > > For such applications, what percentage of all pages at any > given time are reanimated pages? > Is it, say, a couple of percent? Two or three in which case its not > very significant. > Or, is it, say, 50%? Meaning that half of all pages currently in > memory had been serialized to disk, flushed from any in-memory cache > and then, as needed, de-serialized back into a Page. > > Thanks > > Richard > -- > Quis custodiet ipsos custodes > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
