> I dont have any great tools for coming up with these numbers (ie. im using
> println a lot): let me know if they sound out of whack.
check out www.theserverside.com they have some articles on performance and
mention tools you can use.
also they have an article on dependent value objects but I am not sure it
pattern
applies to your situation
----- Original Message -----
From: "Castro, David" <[EMAIL PROTECTED]>
To: "'jBoss'" <[EMAIL PROTECTED]>
Sent: Thursday, February 01, 2001 6:20 PM
Subject: [jBoss-User] Performance help??
> I am trying to improve performance of my application and would like some
> advice from you all...
>
> JBoss - Tomcat Integrated
> 2.0 Final
> Running on a little sparc box
> against Oracle 8.1.7, Oracle XA drivers, installed on the network
>
> I have 3 Entity classes, CMP (jaws), tuned-updates=true, read-only=false
> 1 Session class, CMT, which manages interactions between the front
> end and the entities
> (there are a number of Session classes for admin purposes, but I
> am only concerned about the front end here)
> a couple of jsps to handle logging on and displaying alerts
>
> The 3 entity beans are alert, alertSource, and user.
> Alert stores a pk reference to a user and a pk reference to an
alertSource.
> When a user logs in we look up all the alerts for that user, and all the
> alertSource info for each alert, and display them.
>
> So to view alerts, we do:
> find alerts for user (~1 second)
> for each alert:
> load alert: ~.05 - .1 second
> look up user and alertSource by pk: ~.2 - .3 second
> store alert: ~.15 second
> load alertSource: ~.05 - .1 second (but we usually dont have to do
> this because there are fewer alertSources than alerts)
> store alertSource: ~.05 second
> total: .5 - .6 second per alert
>
> If we are reloading (beans are activated), then all we have to do is the 2
> ejbStore operations and the total goes down to ~.2 second per alert.
>
> If a page has, say, 25 alerts on it, the first number comes to about 14-15
> seconds, the second number comes to about 6 seconds. This seems too long,
> so I am trying to find ways to trim it down.
>
> I dont have any great tools for coming up with these numbers (ie. im using
> println a lot): let me know if they sound out of whack.
>
> Now I should be able to avoid the user look up (since I don't need the
user
> info), but I cant avoid the alertSource look up.
>
> Is there any way I can avoid all the store operations? None of the
methods
> being called from the front end have any side effects, but I am thinking
> that the read-only flag can only be set at the bean level, not the method
> level. Is there anyway to let jaws know that the methods in question do
not
> require a store operation?
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
