Lennart Petersson wrote: > Clustering means better availability, not necessarily better performance.
I though JBoss implemented Cluster for performance and scalability :-)
Anyway I don't want to be polemic, I was just wondering about a good solution to obtain availabilty and increase performance.
We added six more machines to obtain the same tx volume as one instance with caching enabled, but still if I look at one single tx timing is still slower.
> If not > JBoss commit option D will be ok, look at this Seppuku Pattern for > ideas of a solution, possible to implement also in JBoss with some > knowledge (JBossGroup may help you :)
Thank you for the link, I read carefully all the Thread but actually, I really should write a portion of the container if I need transaction.
Davide
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
