On Tue, Oct 7, 2008 at 4:24 PM, Ard Schrijvers <[EMAIL PROTECTED]> wrote: > Hello Matej, > >> I'd really be interested in how exactly did you come to >> conclusion that DiskPageStore writing to disk is the >> bottleneck. Unless your filesystem caching is broken :) > > Hmmm, don't think the filesystem cache is broken. I am working with > filesystem caches and lucene a lot and don't experience really bad > performance. Through when profiling our wicket application with yourkit, > I happened to see a lot of cpu being absorbed in the serialisation / > deserialisation to filesytem >
Again, serialization and writing to filesystem are two completely different things. Are you *really* sure that the writing (which is done in separate thread btw) is really the bottleneck? I have profiled this a lot and the serialization takes signifficantly more time than writing the stuff to disk. But the serialization is necessary, plus the overhead is there only until you run your application in clustered environment. -Matej > Regards Ard > >> Serialization takes a significant part of request processing, >> but that is necessary. >> >> -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 AFAICS. >> > >> > So, before starting to implement one, just wondering >> whether somebody >> > has experience on a memory page store version, >> > >> > Thx for any pointers, >> > >> > Regards Ard >> > >> > [EMAIL PROTECTED] - [EMAIL PROTECTED] - www.onehippo.com >> > ------------------------------------------------------------- >> > Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam >> +31(0)20-5224466 >> > San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA >> > 94952-3329 +1 (707) 773-4646 >> > ------------------------------------------------------------- >> > >> > >> --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
