2 issues: #1 When we do state transfer, we have to copy the state (actually worse: serialize it) into a byte[] buffer. Same happens on the receiver. This means that you will have a memory spike that is double the size of your state. If your state is 400M, then allocate at least 1GB of memory to your JVM
#2 For large states I have an item on the todo list which is to provide a streaming state transfer API, where you transfer chunks (e.g. 10K in size) of state across the network. Your app (sender and receiver) therefore don't have to allocate double the memory of their state, but just an additional <chunk-size>, e.g. 10K. Bela View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843545#3843545 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843545 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
