WADDI WebApplication Performance?

[ru...@je-more.de]

Hi,

Has anybody experience with writing distributed WebApplications
with WADDI and can tell something about its performance and?

I have read the WADDI Faq's but there is no clear advice to write
WADDI designed WebApplication to pass the needs of the Framework...

Waht can i do to write WebApplications (bundled with EJB's and 
JDBC DB access in a *.EAR File) to be WADDI compliant?

Re: WADDI WebApplication Performance?

[Gianny Damour <gi...@optusnet.com.au>]

On 08/05/2008, at 5:06 AM, rudi@je-more.de wrote:

> Sorry!
>
> There a right now some other Question to the Realm of WADDI if have  
> to ask!
>
> Ist there any the same Mechanism like JBoss Farm Deploy of EJB  
> *.EAR, *.WAR Appz?

Hello,

Geronimo provides some basic farming capabilities. This page should  
get you started: http://cwiki.apache.org/GMOxDOC21/farming.html.

Regarding big objects in sessions, I am referring to the objects you  
are binding to HttpSessions as attributes via HttpSession setAttribute 
(String, Object). If these objects are big, then you will pay  
relatively high serialization and network resources costs. Each time  
that a HttpServletRequest completes, the session is replicated to a  
configurable number of nodes. Replication means serialization of the  
session and transport of the resulting byte array to remote nodes.

Thanks,
Gianny


>
> For Example:
> If i do it on JBoss, i deploy my App on 1 Server and this Server  
> will redeploy it to all
> other servers. Even i remove the Application, then it will be safe  
> removed on any MAchine
> of the Farm.
>
> G R

Re: WADDI WebApplication Performance?

["rudi@je-more.de" <ru...@je-more.de>]

Sorry!

There a right now some other Question to the Realm of WADDI if have to ask!

Ist there any the same Mechanism like JBoss Farm Deploy of EJB *.EAR, 
*.WAR Appz?

For Example:
If i do it on JBoss, i deploy my App on 1 Server and this Server will 
redeploy it to all
other servers. Even i remove the Application, then it will be safe 
removed on any MAchine
of the Farm.

G R

Re: WADDI WebApplication Performance?

["rudi@je-more.de" <ru...@je-more.de>]

Hi,
>
> WADI should not impact the performance of your Web-application too 
> much. There are a couple of things to remember when 
> implementing/configuring your Web-applications:
> 1. do not store large objects in HttpSessions. If you really need to 
> store large objects, then I recommend you to enable delta replication. 
> This WIKI page describes how this works 
> http://docs.codehaus.org/display/WADI/1.+Delta+Session+Replication;
> 2. the objects you store in sessions must be serializable; and
> 3. the overhead of state replication increases with the number of 
> replicas to be maintained for a given HttpSession. So, you should 
> define a number of replicas which is a good balance between 
> performance impact caused by the overhead of replication and your HA 
> requirements.

What are large Objects in Sessions?

I use EJB Session Beans and Tomcat Session Beans, is thadt allready big 
- related to WADDI?
(i guess this is the normal Way to do such Kind of dynamic WebAppz.

Greets, R

Re: WADDI WebApplication Performance?

[Gianny Damour <gi...@optusnet.com.au>]

On 07/05/2008, at 6:01 PM, rudi@je-more.de wrote:

> Hi,
>
> Has anybody experience with writing distributed WebApplications
> with WADDI and can tell something about its performance and?
Hello,

WADI should not impact the performance of your Web-application too  
much. There are a couple of things to remember when implementing/ 
configuring your Web-applications:
1. do not store large objects in HttpSessions. If you really need to  
store large objects, then I recommend you to enable delta  
replication. This WIKI page describes how this works http:// 
docs.codehaus.org/display/WADI/1.+Delta+Session+Replication;
2. the objects you store in sessions must be serializable; and
3. the overhead of state replication increases with the number of  
replicas to be maintained for a given HttpSession. So, you should  
define a number of replicas which is a good balance between  
performance impact caused by the overhead of replication and your HA  
requirements.

>
> I have read the WADDI Faq's but there is no clear advice to write
> WADDI designed WebApplication to pass the needs of the Framework...

As long as your objects are Serializable, then WADI can cluster your  
Web-application. As per the above point 1., if you intend to store  
large objects in sessions, then you need to annotate the types of the  
objects you stored in session with @ClusteredState so that wadi-aop  
can identify them and instrument them.

>
> Waht can i do to write WebApplications (bundled with EJB's and
> JDBC DB access in a *.EAR File) to be WADDI compliant?

Nothing special here.

Thanks,
Gianny