You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@beehive.apache.org by "Miller, Michael P" <Mi...@mantech-ist.com> on 2005/04/21 19:44:15 UTC

Performance

I recall the Struts action class being used as a Singleton with the
execute() method invoked as a thread.  Because Beehive is creating sets
of Controller objects for each user session, is it considered a
downgrade in performance as compared to a pure struts app ?

Thanks,
Mike

Re: Performance

Posted by Richard Feit <ri...@bea.com>.
It is a performance hit if you compare it against a Struts action that 
doesn't access any session state.  But the overhead of 
PageFlowController itself is low, so if your Struts action would have 
used session state anyway, there's not much difference.  One thing that 
we need to consider immediately after v1.0 goes out the door is the 
ability to make "stateless" page flows, which are scoped to the request 
and not to the session.  But for an app that would normally hook into 
*some* session state, there shouldn't be a big performance difference.

Rich

Miller, Michael P wrote:

>I recall the Struts action class being used as a Singleton with the
>execute() method invoked as a thread.  Because Beehive is creating sets
>of Controller objects for each user session, is it considered a
>downgrade in performance as compared to a pure struts app ?
>
>Thanks,
>Mike
>
>  
>