On 2/14/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > Its EXACTLY a cache > What isn't a cache is ehcache > > At least not in my point of view > A cache is something you cache something as good as you can but it can be > gone at anytime. > ehcache is not a cache. Its a in memory predefined size list. where some can > drop of and others not > thats not caching. Thats pooling >
Not sure what you mean... and I am not intending to start a flame about it. > A cache is something you cache something as good as you can but it can be > gone at anytime. I wouldn't say this is the definition of a cache, but rather a definition of a flushing policy. Moreover the fact that EHCache allows you to configure different persistent/nonpersistent storage, size and all the rest are quite usefull additions to a caching solution. BR, ./alex -- .w( the_mindstorm )p. _____________________________________ Alexandru Popescu, OSS Evangelist TestNG/Groovy/AspectJ/WebWork/more... Information Queue ~ www.InfoQ.com > And the current caching is because we don't version anything anymore in the > undo buffer doesn't make much > sense. Except if you really make new pages again for pretty much all the > clicks/navigation that you do. > Maybe we should cache the byte[] instead of the pages. What would cost more? > > Because now if you are on page X version 0 > and you click and you go to Page X version 1 > > then go back.. > Previously this was really still an in mem operation. Nowadays it is always > a read from disk.. > maybe we should change that.... > > and i am completely not suprised that ehcache was not performing better. > How could it do that?? Where should the gain come from? > The current impl really grows directly with the hardware you have. ehcache > need to be tweaked exactly > what your system can handle. What do you say then? 200 page? 2000 pages? > What does that cost? > > > johan > > > > On 2/14/07, Matej Knopp < [EMAIL PROTECTED]> wrote: > > I've tried writing a IPageStore using ehcache today, the performance > > wasn't better than what we already have. > > > > And Wicket second level session store is not really a cache, it's works > > differently. > > > > -Matej > > > > Eelco Hillenius wrote: > > > On 2/14/07, Andrew Klochkov < [EMAIL PROTECTED]> wrote: > > >> I looked at pages second level cache implementation in 1.3 and wonder > > >> why not to use ehcache instead? > > > > > > Exactly what I have advocated, and which is why it is had the name > > > 'second level cache'. However, I don't think it should be the default, > > > but rather an (easy to configure) option to plugin anything you like > > > as the 'second level cache', be that an actual caching implementation, > > > a database, (virtual) file system or something else. > > > > > >> It's much more intelligent, configurable > > >> and performant. > > > > > > Keep in mind that we're still in the early stages of it. We're > > > currently tweaking the hell out of it though implementing custom > > > serialization, saving changes in a different thread and only for later > > > versions than the last one (which we keep in memory) etc. The point is > > > that by doing it ourselves, we can tweak exactly for what is needed > > > for Wicket. > > > > > >> For example, it can have part of cache in memory while > > >> swapping less frequently used pages on the disk. > > > > > > It's the idea that we'll have flow over support as well. I don't know > > > whether LRU is the best mechanism though. There are probably smarter > > > ways to do this for Wicket, like basing it on recent activity, > > > available memory/ number of active sessions. I don't know just yet, > > > but it's something that is on our mind for investigating. First things > > > first though. > > > > > > Eelco > > > > > > > ------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net 's Techsay panel and you'll get the chance to share > your > > > opinions on IT & business topics through brief surveys-and earn cash > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > _______________________________________________ > > > Wicket-user mailing list > > > [email protected] > > > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > opinions on IT & business topics through brief surveys-and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Wicket-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
