Re: Prevayler vs Terracotta
Sergey Didenko <[email protected]>
| Newsgroups | gmane.comp.java.prevayler |
|---|---|
| Message-ID | <[email protected]> |
What about the following: Terracotta in persistent mode configured to have a big swap for the virtual JVM. Thus your rarely used objects are in swap and will not be read until they are needed. I have not tried this yet though. On Wed, Nov 11, 2009 at 9:38 PM, William Pietri <[email protected]> wrote: > A client, who does not use Prevayler but is using the hot-in-RAM approach, > has been using 64-bit machines with large JVMs quite happily. I think their > production machine had 16 GB of RAM, with talk of expansion. > > The problem with this approach, though, turns out to be read IO bandwidth > and object deserialization. Their startup times are on the order of 30 > minutes. > > If anybody has interesting solutions (hardware or software) to the long > startup time problem, I'd love to hear about them, as I think that's > Prevayler's Achilles' Heel for scaling. > > William > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion _______________________________________________ "Databases in Memoriam" -- http://www.prevayler.org