Daniel,
I'm not deploying anything that is so "critical". I was just wondering why
the prod 4 deployer is slower than prod 3. I was suprised by this because,
according to testing that I've done, each jboss release seems to be faster
by a factor of 2 to 4. Very impressive in itself. So the fact that something
actually became slower with a newer release was suprising.
I will agree that the auto-deployer does work very effectly now. Good work.
-john
-----Original Message-----
From: Daniel Schulze [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 08, 2000 2:59 PM
To: jBoss
Subject: Re: [jBoss-User] JBoss PROD 4 Deployer is SLow.......
> What happended to the auto-deployer in prod 4. It must be 4 times slower
> than the prod 3 release? Has anyone else noticed this?
Yep, thats right.
There was some overhead added, to allow web.war and app.ear deployment
too. An other point is an code snipped that stops the autodeployer for
exactly one second per application. I added this in the hope to fix the
race condition bug - but as Rickard wrote earlier today this was not the
right target to shoot at... So it will probably be removed in final.
What are you autodeploying that this is critical?
Do you use it for application development on unpacked ejbjar directory
structures? How big are your applications (number of beans or better
number of classes)?
In case of unpacked jars the deployer packs this directories and deploys
the generated packages then - so this may be slower for bigger apps but
I saw this approach as necessary to guaranty for real redeploy (reload
of _all_ classes).
\Daniel
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
