[aspectwerkz-user] From aspectwerkz to aspectJ

 Hi,

Now aspectwerkz has been *merged* into AspectJ, so I am wondering whether it
is better to use AspectJ *NOW*?

Thanks.

Best wishes,
xudong

-----Original Message-----
From: Alexandre Vasseur [mailto:[email protected]] 
Sent: Saturday, June 25, 2005 8:11 PM
To: [email protected]
Subject: Re: [aspectwerkz-user] runtime memory overhead for a large dynamic
deployment scope

Hi
for deployment scope, some information is kept among other data in a map.
You may look at this map size and do your own measurement (Java 5 has a
fairly good objectSize() feature somewhere).

http://cvs.aspectwerkz.codehaus.org/viewrep/aspectwerkz/aspectwerkz4/src/mai
n/org/codehaus/aspectwerkz/transform/inlining/compiler/JoinPointFactory.java
?r=1.8

see map named "COMPILATION_INFO_REPOSITORY "

I would suggest you patch some the source code to add the measurement you
need, or use some profiling tools (if this one can be used in your large
environment), or reproduce thru some sample app (I can send you an app
generator that can generate an app as big as you want to test some the
weaving time and other things)

Alex


On 6/24/05, [email protected] <[email protected]> wrote:
> Hi all,
> 
> Can somebody give me an idea of what is the run-time overhead in terms of
memory for a very large dynamic deployment scope. Say I have:
> 
>  <deployment-scope name="bigScope" expression="execution(* 
> com.mycompany..*(..))"/>
> 
> where com.mycompany and subpackages contains thousands of classes. The
startup time is much slower, of course. But I'm wondering about the memory
footprint created by all those potential join points - is there any? is it
big?
> 
> Thanks,
> Boris
> 
> Visit our website at http://www.ubs.com
> 
> This message contains confidential information and is intended only 
> for the individual named.  If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail.  Please notify 
> the sender immediately by e-mail if you have received this e-mail by 
> mistake and delete this e-mail from your system.
> 
> E-mail transmission cannot be guaranteed to be secure or error-free as 
> information could be intercepted, corrupted, lost, destroyed, arrive 
> late or incomplete, or contain viruses.  The sender therefore does not 
> accept liability for any errors or omissions in the contents of this 
> message which arise as a result of e-mail transmission.  If 
> verification is required please request a hard-copy version.  This 
> message is provided for informational purposes and should not be 
> construed as a solicitation or offer to buy or sell any securities or 
> related financial instruments.
> 
>