, Ard Schrijvers
[EMAIL PROTECTED] wrote:
Hello everybody,
Did anybody perhaps ever implement a memory version of the
AbstractPageStore. Currently, I only see a DiskPageStore, which
happens to be quite a large cpu bottleneck for Windows
users AFAICS.
So, before starting
Hello Igor and Timo,
Sorry for my really way to late response, I was caught up entirely by
some stressful tasks which needed to be finished.
I currently do not have statistics, but I could have a cpu yourkit
snapshot. I have seen up to 75% cpu in the serialization and
deserialization. Recently
Thanks a lot Richard,
I will take a look!
Regards Ard
The wicket integration with terracotta uses an in-memory page map.
The code is here, but will soon be part of the terracotta wicket-tim.
http://www.nabble.com/file/p19826206/TerracottaPageStore.java
TerracottaPageStore.java
.
-Matej
On Fri, Oct 3, 2008 at 3:21 PM, Ard Schrijvers
[EMAIL PROTECTED] wrote:
Hello everybody,
Did anybody perhaps ever implement a memory version of the
AbstractPageStore. Currently, I only see a DiskPageStore, which
happens to be quite a large cpu bottleneck for Windows users
the pointers and fast responses everybody
Regards Ard
On Tue, Oct 7, 2008 at 4:21 PM, Ard Schrijvers
[EMAIL PROTECTED]wrote:
Hello Igor and Timo,
Sorry for my really way to late response, I was caught up
entirely by
some stressful tasks which needed to be finished.
I
the DiskPageStore writes
to disk the TerracottaPageStore writes to http session.
The 100 is number of pages to keep in history as far as i
remember, check the source to be sure.
Ard Schrijvers-3 wrote:
but serialization and writing to disk are 2 different things.
Yes sorry
Hello everybody,
Did anybody perhaps ever implement a memory version of the
AbstractPageStore. Currently, I only see a DiskPageStore, which happens
to be quite a large cpu bottleneck for Windows users AFAICS.
So, before starting to implement one, just wondering whether somebody
has experience
