Databases
StackOverflow2013
Postsdbo
POStartup performance of Spring @Configurable with Compile Time Weaving
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POStartup performance of Spring @Configurable with Compile Time Weaving
    primarykey
    data
    text
    <p>this is my first question on stack overflow, so please be kind.</p> <p>i am running an app with</p> <ul> <li>spring 2.5.x</li> <li>Configurable Annotations</li> <li>Compile time weaving (CTW)</li> <li>maven</li> <li>eclipse/ajdt</li> </ul> <p>I use CTW and everything runs fine. But if i instantiate an annotated class for the first time it takes very long. the second time it is very fast.</p> <p>Looking at the profiler stack trace for the first call i saw 93% of the time is used by org.aspectj.weaver.internal.tools.PointcutExpressionImpl.matchesMethodExecution(Method)</p> <p>In the stack trace of the second call only 1% of the time is used in this method. Even worse: first call takes about 10 times as long as the second call.</p> <p>I was wondering as i thought a weaver is no longer needed with CTW. </p> <p>But it seems that Spring starts analyzing the prototyped bean only as soon as someone calls new on this class. It uses aspectj weaver to analyze what needs to be done and prepares itself to speed up this process for the next call.</p> <p>Does anybody has any experience with speeding up the first call of initializing an annotated class? </p> <p>this is a snippet of my pom:</p> <pre><code> &lt;plugin&gt; &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt; &lt;artifactId&gt;aspectj-maven-plugin&lt;/artifactId&gt; &lt;executions&gt; &lt;execution&gt; &lt;goals&gt; &lt;goal&gt;test-compile&lt;/goal&gt; &lt;goal&gt;compile&lt;/goal&gt; &lt;/goals&gt; &lt;/execution&gt; &lt;/executions&gt; &lt;dependencies&gt; &lt;dependency&gt; &lt;groupId&gt;org.aspectj&lt;/groupId&gt; &lt;artifactId&gt;aspectjtools&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; &lt;/dependencies&gt; &lt;configuration&gt; &lt;verbose&gt;true&lt;/verbose&gt; &lt;complianceLevel&gt;1.5&lt;/complianceLevel&gt; &lt;source&gt;1.5&lt;/source&gt; &lt;showWeaveInfo&gt;true&lt;/showWeaveInfo&gt; &lt;outxml&gt;true&lt;/outxml&gt; &lt;aspectLibraries&gt; &lt;aspectLibrary&gt; &lt;groupId&gt;org.springframework&lt;/groupId&gt; &lt;artifactId&gt;spring-aspects&lt;/artifactId&gt; &lt;/aspectLibrary&gt; &lt;/aspectLibraries&gt; &lt;/configuration&gt; &lt;/plugin&gt; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UScb4
    1. USJanning
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POStartup performance of Spring @Configurable with Compile Time Weaving
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POStartup performance of Spring @Configurable with Compile Time Weaving
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI think this is inherent in CTW. The first call has to do all the heavy lifting to analyze, weave and generate runtime classes, and it's quite expensive.
      singulars
      1. POStartup performance of Spring @Configurable with Compile Time Weaving
      1. USskaffman
    2. COIt should be inherent to Load-time-weaving (LTW), but not to CTW!
      singulars
      1. POStartup performance of Spring @Configurable with Compile Time Weaving
      1. USJanning
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload