Performance Issues between WL 5.1 and WL 6.0

Question

Hello all and thank you in advance,
We're in the process of evaluating Weblogic 6.0 and have noticed a considerable
difference in server response times from Weblogic 5.1(sp9). Testing with a light
load, 5 to 20 threads, our average response time has doubled when using Weblogic
6.0. We've done some reading about the license limitation (5 connection limit)
and tried taking numbers at or below 5 threads, however it still seems that the
response
times are 2 to 2.5 times slower. Does anyone know what the license limitation
of 5 connections means? Is it physical connections, 5 IP addresses ???
We have not tried rebuilding using ejbc2.0 yet (however this is on the list),
and additionaly we are going to try another "fresh" install to see what happeneds.
Everything else we've done is pretty much by the book.
Does anyone have any suggestions, or has Weblogic 6.0 been pigged out by all of
the new features.
Our system consist of multiple servlet, session beans, and entity beans (bean
managed persistance).
Any response is greatly appreciated.
Sean

Answer 1

Dimitri,
I believe that is correct, it is deployment unit which matters. I can't tell
you for sure since I have not tried to deploy exploded format in 6.x, yet.
.raja
"Dimitri Rakitine" <[email protected]> wrote in message
news:[email protected]...
Isn't it the same for WebLogic if you deploy your app in exploded form oras
an EAR as long as it is the same deployment unit?
If web-app and ejb components are separate deployment units thenperformance
will suffer because local RMI optimization will not be used when invokingEJBs
(calls will be by-value vs by-reference).
Raja Mukherjee <[email protected]> wrote:
Is there any reason, why you are deploying your application in the
expanded
format? As I understand in 6.0 if you deploy your application in .earfile
the class loader hierarchy works like (Simplified version)
System Class Loader
|
EJB Class Loader (JAR File)
|
Web Application Class Loader (WAR File)
If you deploy the same application with separate WAR and JAR file, your
class loader will look like
System Class Loader
| |
EJB Class Loader Web Application Class Loader
In general, I have seen 6.0 perform better than 5.1. But again, all my
6.0
deployments are EAR file. I would also cache all JNDI lookups in 6.0. In
5.1, I have only seen marginal gains, but in 6.0 gains are pretty big.
Hope this helps.
.raja
"Rich Llaca" <[email protected]> wrote in message
news:[email protected]...
Hi Rob,
I've been working with Sean to try and figure out our problem. We
really
appreciate your comments and all the feedback we've been getting onthis.
Even though we haven't figured out our problem yet we've learned a lotjust
from everyone's comments.
Your question on deployment is one I've been meaning to ask. Here's
what
we're doing, at least what we've been initially doing.
First of all, our complete application is composed of:
1. servlets receiving routed http input requests,
2. session beans which handle requests from servlets,
3. BMP EJBs which provide the session beans with data and receive datato
make updates/inserts,
4. XML static files which are used along with output coming from thesession
beans to provide a set of output data for each request,
5. XSL files which are used with the output XML to generate the final
web
pages dynamically.
6. everything eventually is output by the handling servlet.
Since we're still in development mode we've been trying to put our
application under 6.0 (we're trying both sp1 and sp2) in expanded form.Our
application is setup under the following typical directory structure:
1. ".../OurDomain/applications/OurApplication".
2. In the OurApplication directory we have directories for our XML and
XSL
files.
3. In the "OurApplication/WEB-INF/web.xml and weblogic.xml" files wehave
the declaration for resources and servlets.
4. In "OurApplication/WEB-INF/lib" we have the jar files containing our
servlets and session beans.
5. Our BMP EJBs are in a seperate jar file. We had been precompiling(with
"ejbc") but now we're trying to let the server do the deploymentcompiling
at server startup.
So my question is; Are we doing something wrong that causing ourperformance
issues? Should we try to structure things differently? We've set things
where the servlets and session beans are basically structured like a
web
app
would be, things that would go into the ".war" file. Is this the right
way
to do this or since we really don't have any static html (all isgenerated
dynamically) should we step back and look at structuring things the waythey
might go into an ".ear" file?
Thanks Again,
Rich
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]...
In general, WLS 6 performs much better than WLS 5.1. First off, make
sure you've installed SP1 (or preferably SP2) for 6.0. These service
packs improve the performance as well as fix bugs.
The most common 5.1-->6.0 performance problem relates to the changes
to
the classloaders.
How are you deploying your application in 6.0? You should deploy a
single EAR file that contains the servlet WARs and the EJB Jars. In
this case, we can optimize the servlet-->EJB calls.
If you deploy them as separate WAR and JAR files, the calls areslower
(call by value) since they are viewed as separate applications by the
server and use separate class loaders.
-- Rob
Sean Cloutier wrote:
Hello all and thank you in advance,
We're in the process of evaluating Weblogic 6.0 and have noticed a
considerable
difference in server response times from Weblogic 5.1(sp9).
Testing
with a light
load, 5 to 20 threads, our average response time has doubled when
using
Weblogic
6.0. We've done some reading about the license limitation (5
connection
limit)
and tried taking numbers at or below 5 threads, however it still
seems
that the
response
times are 2 to 2.5 times slower. Does anyone know what the licenselimitation
of 5 connections means? Is it physical connections, 5 IP addresses
We have not tried rebuilding using ejbc2.0 yet (however this is on
the
list),
and additionaly we are going to try another "fresh" install to see
what
happeneds.
Everything else we've done is pretty much by the book.
Does anyone have any suggestions, or has Weblogic 6.0 been pigged
out
by
all of
the new features.
Our system consist of multiple servlet, session beans, and entity
beans
(bean
managed persistance).
Any response is greatly appreciated.
Sean--
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com
Dimitri