Large deployment issues

Question

Hi,
What would be considered to be a "large" application in terms
of numbers of beans (entity, session) ? I know this may not have a simple answer.
For example, and application that we are considering (J2EE, EJB etc. etc) for
development will have over 250 entity beans and will initially have 40-50 session
beans (this number will creep up over time).
The question here is what type of resources (hardware, software - clustering etc.)
options would we need in order to deploy such an application and also support
a max simultaneuos user number of 200 people ?
Does anyone know of any info on the net ?
Thanks,
Raju

Answer 1

Hi,
I understand that its really the load (# users, # db calls/transactions etc.)
that will really determine whether or not the app will scale.
To be more specific :
1. How long would it take to startup the app server if there are over 300 beans
? (I will probably test this one out this week)
2. Does the number of beans present a challenge / performance issue with regard
to ONLY the sheer number of beans deployed ?
3. This may be a strange one, but does anyone have an idea on "numbers" for EB
caching that weblogic can accomplish ?
I know that this will be dependent on physical memory, but does anyone have any
stats on this ?
Thanks much,
Raju
"Cameron Purdy" <[email protected]> wrote:
Depending on the number of support classes, etc. those 300 EJBs will
probably consume less than 2MB overhead. That's not a small application,
but
it isn't a particularly large application either.
It's not really a question of how many EJB components you have, but how
many
instances get used at runtime. And that is 100% dependent on how the
app is
written.
As far as performance, that is dependent mostly on the number of database
calls and secondly on the number of network ops if the tiers are not
collocated.
As far as scalability, that is dependent mostly on the number of database
calls.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"Raju" <[email protected]> wrote in message
news:[email protected]...
Hi,
What would be considered to be a "large" application in terms
of numbers of beans (entity, session) ? I know this may not have asimple
answer.
For example, and application that we are considering (J2EE, EJB etc.etc)
for
development will have over 250 entity beans and will initially have40-50
session
beans (this number will creep up over time).
The question here is what type of resources (hardware, software -clustering etc.)
options would we need in order to deploy such an application and alsosupport
a max simultaneuos user number of 200 people ?
Does anyone know of any info on the net ?
Thanks,
Raju