You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Michael Wyraz <mi...@evermind.de> on 2013/01/07 15:29:37 UTC

Speed up page compiling

Hi,

we have a big project with Tapestry 5.3. There are many pages, lots of 
components and many links between the pages (@Injects of other pages).
The problem is that after a change, the first page reload takes >5 
seconds on good hardware because there is much work for the tapestry 
page compiler which wastes much time of our developers. Developer 
machines are multicore machines but it seems that compiling is single 
threaded so there's no benefit from that. Are there ways to speed up 
page compiling (e.g. pre-compile components or move them to libraries, 
change the compiler, add some caching or such)?

Regards,
Michael.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling

Posted by Howard Lewis Ship <hl...@gmail.com>.
This is not a trivial undertaking, and it is not an issue for the majority
of Tapestry applications.

I've found that apps that have this issue have gone down the Ubercomponent
route.

That being said, I'd like to fix it, but the amount of time it would take
to even track down how to speed things up is prohibitive; in the past,
similar features (that have a high level of importance to small number of
users) have been addressed by funding.


On Mon, Jan 7, 2013 at 3:59 PM, Bob Harner <bo...@gmail.com> wrote:

> There are also a couple of performance tips at the very bottom of
> http://tapestry.apache.org/class-reloading.html
>
> On Mon, Jan 7, 2013 at 10:33 AM, Thiago H de Paula Figueiredo
> <th...@gmail.com> wrote:
> > On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz
> > <mi...@evermind.de> wrote:
> >
> >> Hi,
> >
> >
> > Hi!
> >
> >
> >> we have a big project with Tapestry 5.3. There are many pages, lots of
> >> components and many links between the pages (@Injects of other pages).
> >> The problem is that after a change, the first page reload takes >5
> seconds
> >> on good hardware because there is much work for the tapestry page
> compiler
> >> which wastes much time of our developers.
> >
> >
> > There isn't a Tapestry page compiler, just a template parser and some
> > internal code that creates the page instances. There's no language
> > transformation, so, for me, it isn't compiling at all.
> >
> > The first thing I think you should do is to do some profiling and check
> > whether these 5+ seconds are really all spent in Tapestry internals or if
> > there's some application-specific processing going on (method calls,
> > database queries, etc).
> >
> > --
> > Thiago H. de Paula Figueiredo
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>


-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

Re: Speed up page compiling

Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Wed, 09 Jan 2013 06:24:19 -0200, Michael Wyraz  
<mi...@evermind.de> wrote:

> Hi,

Hi!

> I had a closer look to the problem (reported by some of our developers):
> There are a few really big pages. Formerly these where separate pages  
> but since we changed everything to ajax navigation, these pages are  
> consolidated to one page.

Howard is way more suited for saying that than me, but I really think  
you've just described the source of your problem: you have a very huge  
page that contains your whole application. It's not just an  
über-component, which is a Tapestry anti-pattern, it's an über-page, which  
is an anti-pattern too. When you change something, you end up making  
Tapestry reload not just one page, but the whole application, as the  
application is inside one page.

There's absolutely no need to consolidate all pages into one for what  
you're doing. Just put different stuff wrapped in blocks, put these blocks  
in different pages, use ComponentSource to get a page instance, getBlock()  
to get the block, the Delegate component or event handler return value to  
render the block, Environment to pass information to the blocks. This  
isn't the only solution (maybe you could @InjectPage the pages, set  
properties on them and use getBody() or getBlock() instead of  
ComponentSource and Environment, but I haven't tested that_, but it's  
basically what the BeanModel-based components (Grid, BeanEditor,  
BeanEditForm, BeanDisplay) do.

-- 
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling (partial solved)

Posted by Michael Wyraz <mi...@evermind.de>.
I eliminated the OGNL problem (simple caching, there are only a few 
unique expressions in the app). The call to file.exists() is also in 
tomcat's original classloader, so there's no difference. Then I profiled 
again.

- Page load takes ~50 seconds with profiler running. Before it took 65 
seconds because of my own ogml caching issue.
- File.exists() takes ~20 seconds: 90% from tomcat's Webapp Classloader 
called  from AssetSourceImpl.getAsset. Probable reason: often-used 
components that injects assets?
- PlasticProxyFactoryImpl.createProxy takes ~9 seconds: most often 
called from PropBindingFactory.newBinding

I'm going to do some more research next week.


> Thank you for the hint - but it returns false.
>
> Today I did some profiling with interesting results. Seems that the 
> current issues are self-made :-(
>
> I installed a trial of YourKit Java Profile which seest so be really 
> usefull. Then I profiled a small page - once after it was changed, 
> once on second reload. The profiler allows to compare both snapshots. 
> CPU tracing slows down the application a lot, so don't wonder about 
> the long times. Here are my results:
>
> The biggest time difference of this test was in
>
> ComponentClassTransformWorker.transform
>
> where the page is build. This happens several times, e.g. when 
> creating a link through link source to a different page that is not 
> already build.
>
> Here most time is consumed by InjectWorker. I tracked it down until 
> spring's BeanFactory.getBeansOfType() - it took several seconds. After 
> some more tests it turned out, that this was because of the profiler. 
> Without it, this BeanFactory.getBeansOfType() was not a speed issue 
> anymore:
>
> Because the profiler slowed down everything, I repeated the same with 
> a big page and without CPU tracing. In this mode, only method time, 
> not invocation count is profiled - it then runs with reasonable speed. 
> On the small page, everything happend within a few milliseconds which 
> is below the threashold of the profiler. The results on the big page 
> are much different:
> Time consumption splits into many different calls during renderPage. I 
> used Hotspot profiling to trace it down to method calls. Here are the 
> biggest time-consumers:
> - Most time goes to initializing OGNL-Bound expressions! This is a 
> home-made issue. We used them in some cases where tapestrys 
> expressions are not sufficient. Seems that there are uses in 
> components that are used very often - I'll to a rework of the code and 
> repeat the tests. Maybe I can cache it.
> - Initializing the assets. I tracked it down to a call to 
> file.exists() in the webapp classloader - we use a special launcher 
> that brings it's own classloader - I'll check if it ist also an issue 
> for the default webapp classloader of tomcat.
>
> I'l going to eliminate these issues and the post my new results.
>
> Regards,
> Michael.
>
>
>
>
>> We have a similiar application architecture, pages with a lot of ajax 
>> components, biggest page reloading takes ~ 5s.
>>
>> Michael, make sure you don't have a debug enabled on the root logger, 
>> it could slow things down.
>>
>> System.out.println(org.slf4j.LoggerFactory.getLogger("xyz123abcRandomLogger").isDebugEnabled()); 
>> - should return false.
>>
>> Denis
>>
>> Jan 10, 2013 v 9:57 AM, Michael Wyraz <mi...@evermind.de>:
>>
>>> I did some further tests on a machine with SSD+HDD, 12 Core  CPU, 
>>> 32GB RAM.
>>> I testet with the biggest page I found, log-level "warn".
>>> The page always needs ~55 seconds to load after webapp start and 
>>> after page modification. There's no difference if it's loaded from 
>>> SSD or from HDD.
>>> During assembly, one core has a load of 80-90%, a second about 
>>> 20-40%. The other cores are idle.
>>>
>>> The page itself requires ~30 seconds to assemble. But it links to a 
>>> similar big page (using linkSource.createPageRenderLinkWithContext) 
>>> - so this page is assebled too. If I change something in the first 
>>> page, both pages are re-assembled on next reload. This doubles the 
>>> reload time. An alternative would be to create the link without 
>>> accessing the other page - but then I would have to re-implememt 
>>> stuff from linksource.
>>>
>>> I have read (and thoght about) the suggestions from Thiago 
>>> (splitting up things to sub pages, look them up via link source). 
>>> Probably this would solve the issue but would be a deep impact in 
>>> application design:
>>> The "big" page does not contain the whole application. It contains 
>>> everything to edit a (big) business entity and it's sub-entities. 
>>> The screens are separated in tabs, each contains a component which 
>>> contains other components like detail/wizard popups, slide-ins and 
>>> so on. The logic for creating each tab is within the responsible 
>>> component (e.g. returning the name of the tab or asking the backend 
>>> to see if the user is allowed to see a certain tab). If I separate 
>>> the components to different pages and lookup/call the pages 
>>> dynamically, tapestry would still have to re-assemble them all on 
>>> changes. To avoid this, I'd move parts of the logic to the master 
>>> page - which would split UI logic across several pages.
>>>
>>>
>>>
>>>> Interesting results, I hope to carve out some time to optimize that 
>>>> code in
>>>> some way. Perhaps some kind of development only cache that could 
>>>> remove
>>>> some of the overhead of analyzing parameter types and usage.
>>>>
>>>> On Wednesday, January 9, 2013, Michael Wyraz wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I had a closer look to the problem (reported by some of our 
>>>>> developers):
>>>>> There are a few really big pages. Formerly these where separate 
>>>>> pages but
>>>>> since we changed everything to ajax navigation, these pages are
>>>>> consolidated to one page. I tested everything on a machine that 
>>>>> runs the
>>>>> workspace on a hardware raid on SSDs where IO performance should 
>>>>> not be the
>>>>> problem at all. After starting the webapp, the first load of this 
>>>>> page
>>>>> takes ~30 seconds. I changed tapestrys log level to "ALL" and 
>>>>> restarted -
>>>>> the page load took >4 minutes and printed several 100.000 log 
>>>>> lines. Most
>>>>> log lines (and probably most time) is in ParameterWorker. It takes 
>>>>> about
>>>>> 90% of the component assembling time. Subsequent reloads take just 
>>>>> a few
>>>>> milliseconds. After modifying the page, reload takes again >4 
>>>>> minutes with
>>>>> full debug.
>>>>> Most time is spend in ParameterWorker (logs from line 319, 329 and 
>>>>> 340).
>>>>> Another place which takes lot time is Registry (logs from line 67 
>>>>> and 81).
>>>>>
>>>>> Since the code in ParameterWorker is called some 100.000 or millions
>>>>> times, speedup there would bring a big performance plus.
>>>>>
>>>>> But maybe there are other ways to improve performance?
>>>>>
>>>>>   There are also a couple of performance tips at the very bottom of
>>>>>> http://tapestry.apache.org/**class-reloading.html<http://tapestry.apache.org/class-reloading.html> 
>>>>>>
>>>>>>
>>>>>> On Mon, Jan 7, 2013 at 10:33 AM, Thiago H de Paula Figueiredo
>>>>>> <th...@gmail.com> wrote:
>>>>>>
>>>>>>> On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz
>>>>>>> <mi...@evermind.de> wrote:
>>>>>>>
>>>>>>>   Hi,
>>>>>>> Hi!
>>>>>>>
>>>>>>>
>>>>>>>   we have a big project with Tapestry 5.3. There are many pages, 
>>>>>>> lots of
>>>>>>>> components and many links between the pages (@Injects of other 
>>>>>>>> pages).
>>>>>>>> The problem is that after a change, the first page reload takes >5
>>>>>>>> seconds
>>>>>>>> on good hardware because there is much work for the tapestry page
>>>>>>>> compiler
>>>>>>>> which wastes much time of our developers.
>>>>>>>>
>>>>>>> There isn't a Tapestry page compiler, just a template parser and 
>>>>>>> some
>>>>>>> internal code that creates the page instances. There's no language
>>>>>>> transformation, so, for me, it isn't compiling at all.
>>>>>>>
>>>>>>> The first thing I think you should do is to do some profiling 
>>>>>>> and check
>>>>>>> whether these 5+ seconds are really all spent in Tapestry 
>>>>>>> internals or if
>>>>>>> there's some application-specific processing going on (method 
>>>>>>> calls,
>>>>>>> database queries, etc).
>>>>>>>
>>>>>>> -- 
>>>>>>> Thiago H. de Paula Figueiredo
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------**------------------------------**
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>>
>>>>>>> ------------------------------**------------------------------**
>>>>>> ---------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>
>>>>>>
>>>>> -- 
>>>>> Mit freundlichen Grüßen / Regards
>>>>>
>>>>> Michael Wyraz
>>>>>
>>>>> evermind GmbH
>>>>> Schorlemmerstraße 1
>>>>> 04155 Leipzig
>>>>>
>>>>> Tel.:       +49 (0)341-25 39 66 - 0
>>>>> Fax:        +49 (0)341-25 39 66 - 1
>>>>> Funk:       +49 (0)177-73 00 00 3
>>>>> E-Mail:     michael.wyraz@evermind.de
>>>>>
>>>>> HRB: 21586
>>>>> Amtsgericht Leipzig
>>>>>
>>>>> Geschäftsführer:
>>>>> Christoph Klemm
>>>>> Thomas Grünert
>>>>> Michael Wyraz
>>>>>
>>>>>
>>>>> ------------------------------**------------------------------**--------- 
>>>>>
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>
>>> -- 
>>> Mit freundlichen Grüßen / Regards
>>>
>>> Michael Wyraz
>>>
>>> evermind GmbH
>>> Schorlemmerstraße 1
>>> 04155 Leipzig
>>>
>>> Tel.:       +49 (0)341-25 39 66 - 0
>>> Fax:        +49 (0)341-25 39 66 - 1
>>> Funk:       +49 (0)177-73 00 00 3
>>> E-Mail:     michael.wyraz@evermind.de
>>>
>>> HRB: 21586
>>> Amtsgericht Leipzig
>>>
>>> Geschäftsführer:
>>> Christoph Klemm
>>> Thomas Grünert
>>> Michael Wyraz
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling - detailed analysis

Posted by Michael Wyraz <mi...@evermind.de>.
Hi,

I spent some more time in profiling/debugging. I added caching for all 
my OGNL bindings so that's no issue anymore. I add Cachring for tomcat's 
WebappClassloader.findResource which was a big hotspot. I cut the link 
between my 3 big pages so that only 1 page is loaded at once.
Loading still takes ~18 seconds, here are the remaining time eaters:
- PlasticProxyFactoryImpl.createProxy 8 seconds (7 seconds own time)
- ClassLoader.loadClass 5 seconds (3.2 seconds own time)
   - called often from ComponentInstantiatorSourceImpl.getInstantiator
   - called often from PlasticProxyFactoryImpl.createProxy
- ArrayList.toArray 2 seconds
   - called often from StringInternerImpl.format(String,Object[])
- File.exists() 2 seconds
   - called often from AssetSourceImpl.getAsset
- StringInternerImpl.format 1.3 seconds own time
- InitializeActivePageName.handlePageRender 1.4 seconds own time
- WebappClassLoader.getResource 1 second own time
   - called often from AssetSourceImpl.getAsset
- AssetSourceImpl.getAsset 1 second own time

"own time" means the time spent within the method itself (excluding the 
time spent in other called method from within this method).

It's possible to speed up some things with optimizations but the best 
approach would be a development-only proxy.

Regards,
Michael.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling (partial solved)

Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Fri, 11 Jan 2013 10:35:54 -0200, Michael Wyraz  
<mi...@evermind.de> wrote:

> I'm going to do so. Most are lamda expressions like  
> "ognl:disabled?'cssclassdisabled':'cssclassnormal'".

You could write a binding prefix for doing this kind of stuff, as you said  
this is quite common in your code.

>> It would also be interesting if you did the same profiling in Jetty,  
>> which is usually faster and better implemented than Tomcat.
> I'd wonder if it would be so. Accessing context resources will always  
> hit the filesystem. Accessing file metadata many times (e.g.  
> File.exists()) is terible slow (at least on windows).

Testing this in Linux would be quite interesting too, but I know I'm  
asking too much now. :) (Full-time Linux user here except some Windows  
time for games I cannot run in Linux).

-- 
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling (partial solved)

Posted by Michael Wyraz <mi...@evermind.de>.
Am 11.01.2013 12:02, schrieb Thiago H de Paula Figueiredo:
> On Fri, 11 Jan 2013 08:01:27 -0200, Michael Wyraz 
> <mi...@evermind.de> wrote:
>
>> - Most time goes to initializing OGNL-Bound expressions! This is a 
>> home-made issue. We used them in some cases where tapestrys 
>> expressions are not sufficient. Seems that there are uses in 
>> components that are used very often - I'll to a rework of the code 
>> and repeat the tests. Maybe I can cache it.
>
> Maybe, instead, you should gradually ditch OGNL and replace its usage 
> by methods and Tapestry expressions are faster. That's the recommended 
> thing to do anyway: move logic from template to class.
>
> Tapestry, out-of-the-box, doesn't use OGNL since T5.0 (just reminding 
> that for people who read this and remember Tapestry 4, that did use 
> OGNL out-of-the-box).
I'm going to do so. Most are lamda expressions like 
"ognl:disabled?'cssclassdisabled':'cssclassnormal'". I added some 
caching, removing almost all overhead of ognl compiling (reducing from 
16 to 1 second on the big page).
>
>> - Initializing the assets. I tracked it down to a call to 
>> file.exists() in the webapp classloader - we use a special launcher 
>> that brings it's own classloader - I'll check if it ist also an issue 
>> for the default webapp classloader of tomcat.
>
> It would also be interesting if you did the same profiling in Jetty, 
> which is usually faster and better implemented than Tomcat.
I'd wonder if it would be so. Accessing context resources will always 
hit the filesystem. Accessing file metadata many times (e.g. 
File.exists()) is terible slow (at least on windows).
>
> By the way, it seems you tried to include a couple images in your 
> e-mail, but didn't or they were lost somewhere between your e-mail 
> client and the mailing list.
>
I guess that's thunderbird which replaced some smileys by graphics. I 
did not attach anything.

Regards,
Michael.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling (partial solved)

Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Fri, 11 Jan 2013 08:01:27 -0200, Michael Wyraz  
<mi...@evermind.de> wrote:

> - Most time goes to initializing OGNL-Bound expressions! This is a  
> home-made issue. We used them in some cases where tapestrys expressions  
> are not sufficient. Seems that there are uses in components that are  
> used very often - I'll to a rework of the code and repeat the tests.  
> Maybe I can cache it.

Maybe, instead, you should gradually ditch OGNL and replace its usage by  
methods and Tapestry expressions are faster. That's the recommended thing  
to do anyway: move logic from template to class.

Tapestry, out-of-the-box, doesn't use OGNL since T5.0 (just reminding that  
for people who read this and remember Tapestry 4, that did use OGNL  
out-of-the-box).

> - Initializing the assets. I tracked it down to a call to file.exists()  
> in the webapp classloader - we use a special launcher that brings it's  
> own classloader - I'll check if it ist also an issue for the default  
> webapp classloader of tomcat.

It would also be interesting if you did the same profiling in Jetty, which  
is usually faster and better implemented than Tomcat.

By the way, it seems you tried to include a couple images in your e-mail,  
but didn't or they were lost somewhere between your e-mail client and the  
mailing list.

-- 
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling (partial solved)

Posted by Michael Wyraz <mi...@evermind.de>.
Thank you for the hint - but it returns false.

Today I did some profiling with interesting results. Seems that the 
current issues are self-made :-(

I installed a trial of YourKit Java Profile which seest so be really 
usefull. Then I profiled a small page - once after it was changed, once 
on second reload. The profiler allows to compare both snapshots. CPU 
tracing slows down the application a lot, so don't wonder about the long 
times. Here are my results:

The biggest time difference of this test was in

ComponentClassTransformWorker.transform

where the page is build. This happens several times, e.g. when creating 
a link through link source to a different page that is not already build.

Here most time is consumed by InjectWorker. I tracked it down until 
spring's BeanFactory.getBeansOfType() - it took several seconds. After 
some more tests it turned out, that this was because of the profiler. 
Without it, this BeanFactory.getBeansOfType() was not a speed issue anymore:

Because the profiler slowed down everything, I repeated the same with a 
big page and without CPU tracing. In this mode, only method time, not 
invocation count is profiled - it then runs with reasonable speed. On 
the small page, everything happend within a few milliseconds which is 
below the threashold of the profiler. The results on the big page are 
much different:
Time consumption splits into many different calls during renderPage. I 
used Hotspot profiling to trace it down to method calls. Here are the 
biggest time-consumers:
- Most time goes to initializing OGNL-Bound expressions! This is a 
home-made issue. We used them in some cases where tapestrys expressions 
are not sufficient. Seems that there are uses in components that are 
used very often - I'll to a rework of the code and repeat the tests. 
Maybe I can cache it.
- Initializing the assets. I tracked it down to a call to file.exists() 
in the webapp classloader - we use a special launcher that brings it's 
own classloader - I'll check if it ist also an issue for the default 
webapp classloader of tomcat.

I'l going to eliminate these issues and the post my new results.

Regards,
Michael.




> We have a similiar application architecture, pages with a lot of ajax components, biggest page reloading takes ~ 5s.
>
> Michael, make sure you don't have a debug enabled on the root logger, it could slow things down.
>
> System.out.println(org.slf4j.LoggerFactory.getLogger("xyz123abcRandomLogger").isDebugEnabled()); - should return false.
>
> Denis
>
> Jan 10, 2013 v 9:57 AM, Michael Wyraz <mi...@evermind.de>:
>
>> I did some further tests on a machine with SSD+HDD, 12 Core  CPU, 32GB RAM.
>> I testet with the biggest page I found, log-level "warn".
>> The page always needs ~55 seconds to load after webapp start and after page modification. There's no difference if it's loaded from SSD or from HDD.
>> During assembly, one core has a load of 80-90%, a second about 20-40%. The other cores are idle.
>>
>> The page itself requires ~30 seconds to assemble. But it links to a similar big page (using linkSource.createPageRenderLinkWithContext) - so this page is assebled too. If I change something in the first page, both pages are re-assembled on next reload. This doubles the reload time. An alternative would be to create the link without accessing the other page - but then I would have to re-implememt stuff from linksource.
>>
>> I have read (and thoght about) the suggestions from Thiago (splitting up things to sub pages, look them up via link source). Probably this would solve the issue but would be a deep impact in application design:
>> The "big" page does not contain the whole application. It contains everything to edit a (big) business entity and it's sub-entities. The screens are separated in tabs, each contains a component which contains other components like detail/wizard popups, slide-ins and so on. The logic for creating each tab is within the responsible component (e.g. returning the name of the tab or asking the backend to see if the user is allowed to see a certain tab). If I separate the components to different pages and lookup/call the pages dynamically, tapestry would still have to re-assemble them all on changes. To avoid this, I'd move parts of the logic to the master page - which would split UI logic across several pages.
>>
>>
>>
>>> Interesting results, I hope to carve out some time to optimize that code in
>>> some way. Perhaps some kind of development only cache that could remove
>>> some of the overhead of analyzing parameter types and usage.
>>>
>>> On Wednesday, January 9, 2013, Michael Wyraz wrote:
>>>
>>>> Hi,
>>>>
>>>> I had a closer look to the problem (reported by some of our developers):
>>>> There are a few really big pages. Formerly these where separate pages but
>>>> since we changed everything to ajax navigation, these pages are
>>>> consolidated to one page. I tested everything on a machine that runs the
>>>> workspace on a hardware raid on SSDs where IO performance should not be the
>>>> problem at all. After starting the webapp, the first load of this page
>>>> takes ~30 seconds. I changed tapestrys log level to "ALL" and restarted -
>>>> the page load took >4 minutes and printed several 100.000 log lines. Most
>>>> log lines (and probably most time) is in ParameterWorker. It takes about
>>>> 90% of the component assembling time. Subsequent reloads take just a few
>>>> milliseconds. After modifying the page, reload takes again >4 minutes with
>>>> full debug.
>>>> Most time is spend in ParameterWorker (logs from line 319, 329 and 340).
>>>> Another place which takes lot time is Registry (logs from line 67 and 81).
>>>>
>>>> Since the code in ParameterWorker is called some 100.000 or millions
>>>> times, speedup there would bring a big performance plus.
>>>>
>>>> But maybe there are other ways to improve performance?
>>>>
>>>>   There are also a couple of performance tips at the very bottom of
>>>>> http://tapestry.apache.org/**class-reloading.html<http://tapestry.apache.org/class-reloading.html>
>>>>>
>>>>> On Mon, Jan 7, 2013 at 10:33 AM, Thiago H de Paula Figueiredo
>>>>> <th...@gmail.com> wrote:
>>>>>
>>>>>> On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz
>>>>>> <mi...@evermind.de> wrote:
>>>>>>
>>>>>>   Hi,
>>>>>> Hi!
>>>>>>
>>>>>>
>>>>>>   we have a big project with Tapestry 5.3. There are many pages, lots of
>>>>>>> components and many links between the pages (@Injects of other pages).
>>>>>>> The problem is that after a change, the first page reload takes >5
>>>>>>> seconds
>>>>>>> on good hardware because there is much work for the tapestry page
>>>>>>> compiler
>>>>>>> which wastes much time of our developers.
>>>>>>>
>>>>>> There isn't a Tapestry page compiler, just a template parser and some
>>>>>> internal code that creates the page instances. There's no language
>>>>>> transformation, so, for me, it isn't compiling at all.
>>>>>>
>>>>>> The first thing I think you should do is to do some profiling and check
>>>>>> whether these 5+ seconds are really all spent in Tapestry internals or if
>>>>>> there's some application-specific processing going on (method calls,
>>>>>> database queries, etc).
>>>>>>
>>>>>> --
>>>>>> Thiago H. de Paula Figueiredo
>>>>>>
>>>>>>
>>>>>> ------------------------------**------------------------------**
>>>>>> ---------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>
>>>>>>   ------------------------------**------------------------------**
>>>>> ---------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>> --
>>>> Mit freundlichen Grüßen / Regards
>>>>
>>>> Michael Wyraz
>>>>
>>>> evermind GmbH
>>>> Schorlemmerstraße 1
>>>> 04155 Leipzig
>>>>
>>>> Tel.:       +49 (0)341-25 39 66 - 0
>>>> Fax:        +49 (0)341-25 39 66 - 1
>>>> Funk:       +49 (0)177-73 00 00 3
>>>> E-Mail:     michael.wyraz@evermind.de
>>>>
>>>> HRB: 21586
>>>> Amtsgericht Leipzig
>>>>
>>>> Geschäftsführer:
>>>> Christoph Klemm
>>>> Thomas Grünert
>>>> Michael Wyraz
>>>>
>>>>
>>>> ------------------------------**------------------------------**---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>
>> -- 
>> Mit freundlichen Grüßen / Regards
>>
>> Michael Wyraz
>>
>> evermind GmbH
>> Schorlemmerstraße 1
>> 04155 Leipzig
>>
>> Tel.:       +49 (0)341-25 39 66 - 0
>> Fax:        +49 (0)341-25 39 66 - 1
>> Funk:       +49 (0)177-73 00 00 3
>> E-Mail:     michael.wyraz@evermind.de
>>
>> HRB: 21586
>> Amtsgericht Leipzig
>>
>> Geschäftsführer:
>> Christoph Klemm
>> Thomas Grünert
>> Michael Wyraz
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling

Posted by Denis Stepanov <de...@gmail.com>.
We have a similiar application architecture, pages with a lot of ajax components, biggest page reloading takes ~ 5s.

Michael, make sure you don't have a debug enabled on the root logger, it could slow things down.

System.out.println(org.slf4j.LoggerFactory.getLogger("xyz123abcRandomLogger").isDebugEnabled()); - should return false.

Denis

Jan 10, 2013 v 9:57 AM, Michael Wyraz <mi...@evermind.de>:

> I did some further tests on a machine with SSD+HDD, 12 Core  CPU, 32GB RAM.
> I testet with the biggest page I found, log-level "warn".
> The page always needs ~55 seconds to load after webapp start and after page modification. There's no difference if it's loaded from SSD or from HDD.
> During assembly, one core has a load of 80-90%, a second about 20-40%. The other cores are idle.
> 
> The page itself requires ~30 seconds to assemble. But it links to a similar big page (using linkSource.createPageRenderLinkWithContext) - so this page is assebled too. If I change something in the first page, both pages are re-assembled on next reload. This doubles the reload time. An alternative would be to create the link without accessing the other page - but then I would have to re-implememt stuff from linksource.
> 
> I have read (and thoght about) the suggestions from Thiago (splitting up things to sub pages, look them up via link source). Probably this would solve the issue but would be a deep impact in application design:
> The "big" page does not contain the whole application. It contains everything to edit a (big) business entity and it's sub-entities. The screens are separated in tabs, each contains a component which contains other components like detail/wizard popups, slide-ins and so on. The logic for creating each tab is within the responsible component (e.g. returning the name of the tab or asking the backend to see if the user is allowed to see a certain tab). If I separate the components to different pages and lookup/call the pages dynamically, tapestry would still have to re-assemble them all on changes. To avoid this, I'd move parts of the logic to the master page - which would split UI logic across several pages.
> 
> 
> 
>> Interesting results, I hope to carve out some time to optimize that code in
>> some way. Perhaps some kind of development only cache that could remove
>> some of the overhead of analyzing parameter types and usage.
>> 
>> On Wednesday, January 9, 2013, Michael Wyraz wrote:
>> 
>>> Hi,
>>> 
>>> I had a closer look to the problem (reported by some of our developers):
>>> There are a few really big pages. Formerly these where separate pages but
>>> since we changed everything to ajax navigation, these pages are
>>> consolidated to one page. I tested everything on a machine that runs the
>>> workspace on a hardware raid on SSDs where IO performance should not be the
>>> problem at all. After starting the webapp, the first load of this page
>>> takes ~30 seconds. I changed tapestrys log level to "ALL" and restarted -
>>> the page load took >4 minutes and printed several 100.000 log lines. Most
>>> log lines (and probably most time) is in ParameterWorker. It takes about
>>> 90% of the component assembling time. Subsequent reloads take just a few
>>> milliseconds. After modifying the page, reload takes again >4 minutes with
>>> full debug.
>>> Most time is spend in ParameterWorker (logs from line 319, 329 and 340).
>>> Another place which takes lot time is Registry (logs from line 67 and 81).
>>> 
>>> Since the code in ParameterWorker is called some 100.000 or millions
>>> times, speedup there would bring a big performance plus.
>>> 
>>> But maybe there are other ways to improve performance?
>>> 
>>>  There are also a couple of performance tips at the very bottom of
>>>> http://tapestry.apache.org/**class-reloading.html<http://tapestry.apache.org/class-reloading.html>
>>>> 
>>>> On Mon, Jan 7, 2013 at 10:33 AM, Thiago H de Paula Figueiredo
>>>> <th...@gmail.com> wrote:
>>>> 
>>>>> On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz
>>>>> <mi...@evermind.de> wrote:
>>>>> 
>>>>>  Hi,
>>>>> Hi!
>>>>> 
>>>>> 
>>>>>  we have a big project with Tapestry 5.3. There are many pages, lots of
>>>>>> components and many links between the pages (@Injects of other pages).
>>>>>> The problem is that after a change, the first page reload takes >5
>>>>>> seconds
>>>>>> on good hardware because there is much work for the tapestry page
>>>>>> compiler
>>>>>> which wastes much time of our developers.
>>>>>> 
>>>>> There isn't a Tapestry page compiler, just a template parser and some
>>>>> internal code that creates the page instances. There's no language
>>>>> transformation, so, for me, it isn't compiling at all.
>>>>> 
>>>>> The first thing I think you should do is to do some profiling and check
>>>>> whether these 5+ seconds are really all spent in Tapestry internals or if
>>>>> there's some application-specific processing going on (method calls,
>>>>> database queries, etc).
>>>>> 
>>>>> --
>>>>> Thiago H. de Paula Figueiredo
>>>>> 
>>>>> 
>>>>> ------------------------------**------------------------------**
>>>>> ---------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>> 
>>>>>  ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>> 
>>>> 
>>> --
>>> Mit freundlichen Grüßen / Regards
>>> 
>>> Michael Wyraz
>>> 
>>> evermind GmbH
>>> Schorlemmerstraße 1
>>> 04155 Leipzig
>>> 
>>> Tel.:       +49 (0)341-25 39 66 - 0
>>> Fax:        +49 (0)341-25 39 66 - 1
>>> Funk:       +49 (0)177-73 00 00 3
>>> E-Mail:     michael.wyraz@evermind.de
>>> 
>>> HRB: 21586
>>> Amtsgericht Leipzig
>>> 
>>> Geschäftsführer:
>>> Christoph Klemm
>>> Thomas Grünert
>>> Michael Wyraz
>>> 
>>> 
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>> 
>>> 
> 
> 
> -- 
> Mit freundlichen Grüßen / Regards
> 
> Michael Wyraz
> 
> evermind GmbH
> Schorlemmerstraße 1
> 04155 Leipzig
> 
> Tel.:       +49 (0)341-25 39 66 - 0
> Fax:        +49 (0)341-25 39 66 - 1
> Funk:       +49 (0)177-73 00 00 3
> E-Mail:     michael.wyraz@evermind.de
> 
> HRB: 21586
> Amtsgericht Leipzig
> 
> Geschäftsführer:
> Christoph Klemm
> Thomas Grünert
> Michael Wyraz
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling

Posted by Michael Wyraz <mi...@evermind.de>.
I did some further tests on a machine with SSD+HDD, 12 Core  CPU, 32GB RAM.
I testet with the biggest page I found, log-level "warn".
The page always needs ~55 seconds to load after webapp start and after 
page modification. There's no difference if it's loaded from SSD or from 
HDD.
During assembly, one core has a load of 80-90%, a second about 20-40%. 
The other cores are idle.

The page itself requires ~30 seconds to assemble. But it links to a 
similar big page (using linkSource.createPageRenderLinkWithContext) - so 
this page is assebled too. If I change something in the first page, both 
pages are re-assembled on next reload. This doubles the reload time. An 
alternative would be to create the link without accessing the other page 
- but then I would have to re-implememt stuff from linksource.

I have read (and thoght about) the suggestions from Thiago (splitting up 
things to sub pages, look them up via link source). Probably this would 
solve the issue but would be a deep impact in application design:
The "big" page does not contain the whole application. It contains 
everything to edit a (big) business entity and it's sub-entities. The 
screens are separated in tabs, each contains a component which contains 
other components like detail/wizard popups, slide-ins and so on. The 
logic for creating each tab is within the responsible component (e.g. 
returning the name of the tab or asking the backend to see if the user 
is allowed to see a certain tab). If I separate the components to 
different pages and lookup/call the pages dynamically, tapestry would 
still have to re-assemble them all on changes. To avoid this, I'd move 
parts of the logic to the master page - which would split UI logic 
across several pages.



> Interesting results, I hope to carve out some time to optimize that code in
> some way. Perhaps some kind of development only cache that could remove
> some of the overhead of analyzing parameter types and usage.
>
> On Wednesday, January 9, 2013, Michael Wyraz wrote:
>
>> Hi,
>>
>> I had a closer look to the problem (reported by some of our developers):
>> There are a few really big pages. Formerly these where separate pages but
>> since we changed everything to ajax navigation, these pages are
>> consolidated to one page. I tested everything on a machine that runs the
>> workspace on a hardware raid on SSDs where IO performance should not be the
>> problem at all. After starting the webapp, the first load of this page
>> takes ~30 seconds. I changed tapestrys log level to "ALL" and restarted -
>> the page load took >4 minutes and printed several 100.000 log lines. Most
>> log lines (and probably most time) is in ParameterWorker. It takes about
>> 90% of the component assembling time. Subsequent reloads take just a few
>> milliseconds. After modifying the page, reload takes again >4 minutes with
>> full debug.
>> Most time is spend in ParameterWorker (logs from line 319, 329 and 340).
>> Another place which takes lot time is Registry (logs from line 67 and 81).
>>
>> Since the code in ParameterWorker is called some 100.000 or millions
>> times, speedup there would bring a big performance plus.
>>
>> But maybe there are other ways to improve performance?
>>
>>   There are also a couple of performance tips at the very bottom of
>>> http://tapestry.apache.org/**class-reloading.html<http://tapestry.apache.org/class-reloading.html>
>>>
>>> On Mon, Jan 7, 2013 at 10:33 AM, Thiago H de Paula Figueiredo
>>> <th...@gmail.com> wrote:
>>>
>>>> On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz
>>>> <mi...@evermind.de> wrote:
>>>>
>>>>   Hi,
>>>> Hi!
>>>>
>>>>
>>>>   we have a big project with Tapestry 5.3. There are many pages, lots of
>>>>> components and many links between the pages (@Injects of other pages).
>>>>> The problem is that after a change, the first page reload takes >5
>>>>> seconds
>>>>> on good hardware because there is much work for the tapestry page
>>>>> compiler
>>>>> which wastes much time of our developers.
>>>>>
>>>> There isn't a Tapestry page compiler, just a template parser and some
>>>> internal code that creates the page instances. There's no language
>>>> transformation, so, for me, it isn't compiling at all.
>>>>
>>>> The first thing I think you should do is to do some profiling and check
>>>> whether these 5+ seconds are really all spent in Tapestry internals or if
>>>> there's some application-specific processing going on (method calls,
>>>> database queries, etc).
>>>>
>>>> --
>>>> Thiago H. de Paula Figueiredo
>>>>
>>>>
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>   ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>> --
>> Mit freundlichen Grüßen / Regards
>>
>> Michael Wyraz
>>
>> evermind GmbH
>> Schorlemmerstraße 1
>> 04155 Leipzig
>>
>> Tel.:       +49 (0)341-25 39 66 - 0
>> Fax:        +49 (0)341-25 39 66 - 1
>> Funk:       +49 (0)177-73 00 00 3
>> E-Mail:     michael.wyraz@evermind.de
>>
>> HRB: 21586
>> Amtsgericht Leipzig
>>
>> Geschäftsführer:
>> Christoph Klemm
>> Thomas Grünert
>> Michael Wyraz
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>


-- 
Mit freundlichen Grüßen / Regards

Michael Wyraz

evermind GmbH
Schorlemmerstraße 1
04155 Leipzig

Tel.:       +49 (0)341-25 39 66 - 0
Fax:        +49 (0)341-25 39 66 - 1
Funk:       +49 (0)177-73 00 00 3
E-Mail:     michael.wyraz@evermind.de

HRB: 21586
Amtsgericht Leipzig

Geschäftsführer:
Christoph Klemm
Thomas Grünert
Michael Wyraz


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling

Posted by Howard Lewis Ship <hl...@gmail.com>.
Interesting results, I hope to carve out some time to optimize that code in
some way. Perhaps some kind of development only cache that could remove
some of the overhead of analyzing parameter types and usage.

On Wednesday, January 9, 2013, Michael Wyraz wrote:

> Hi,
>
> I had a closer look to the problem (reported by some of our developers):
> There are a few really big pages. Formerly these where separate pages but
> since we changed everything to ajax navigation, these pages are
> consolidated to one page. I tested everything on a machine that runs the
> workspace on a hardware raid on SSDs where IO performance should not be the
> problem at all. After starting the webapp, the first load of this page
> takes ~30 seconds. I changed tapestrys log level to "ALL" and restarted -
> the page load took >4 minutes and printed several 100.000 log lines. Most
> log lines (and probably most time) is in ParameterWorker. It takes about
> 90% of the component assembling time. Subsequent reloads take just a few
> milliseconds. After modifying the page, reload takes again >4 minutes with
> full debug.
> Most time is spend in ParameterWorker (logs from line 319, 329 and 340).
> Another place which takes lot time is Registry (logs from line 67 and 81).
>
> Since the code in ParameterWorker is called some 100.000 or millions
> times, speedup there would bring a big performance plus.
>
> But maybe there are other ways to improve performance?
>
>  There are also a couple of performance tips at the very bottom of
>> http://tapestry.apache.org/**class-reloading.html<http://tapestry.apache.org/class-reloading.html>
>>
>> On Mon, Jan 7, 2013 at 10:33 AM, Thiago H de Paula Figueiredo
>> <th...@gmail.com> wrote:
>>
>>> On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz
>>> <mi...@evermind.de> wrote:
>>>
>>>  Hi,
>>>>
>>>
>>> Hi!
>>>
>>>
>>>  we have a big project with Tapestry 5.3. There are many pages, lots of
>>>> components and many links between the pages (@Injects of other pages).
>>>> The problem is that after a change, the first page reload takes >5
>>>> seconds
>>>> on good hardware because there is much work for the tapestry page
>>>> compiler
>>>> which wastes much time of our developers.
>>>>
>>>
>>> There isn't a Tapestry page compiler, just a template parser and some
>>> internal code that creates the page instances. There's no language
>>> transformation, so, for me, it isn't compiling at all.
>>>
>>> The first thing I think you should do is to do some profiling and check
>>> whether these 5+ seconds are really all spent in Tapestry internals or if
>>> there's some application-specific processing going on (method calls,
>>> database queries, etc).
>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>>
>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>  ------------------------------**------------------------------**
>> ---------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
> --
> Mit freundlichen Grüßen / Regards
>
> Michael Wyraz
>
> evermind GmbH
> Schorlemmerstraße 1
> 04155 Leipzig
>
> Tel.:       +49 (0)341-25 39 66 - 0
> Fax:        +49 (0)341-25 39 66 - 1
> Funk:       +49 (0)177-73 00 00 3
> E-Mail:     michael.wyraz@evermind.de
>
> HRB: 21586
> Amtsgericht Leipzig
>
> Geschäftsführer:
> Christoph Klemm
> Thomas Grünert
> Michael Wyraz
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>

-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

Re: Speed up page compiling

Posted by Michael Wyraz <mi...@evermind.de>.
Hi,

I had a closer look to the problem (reported by some of our developers):
There are a few really big pages. Formerly these where separate pages 
but since we changed everything to ajax navigation, these pages are 
consolidated to one page. I tested everything on a machine that runs the 
workspace on a hardware raid on SSDs where IO performance should not be 
the problem at all. After starting the webapp, the first load of this 
page takes ~30 seconds. I changed tapestrys log level to "ALL" and 
restarted - the page load took >4 minutes and printed several 100.000 
log lines. Most log lines (and probably most time) is in 
ParameterWorker. It takes about 90% of the component assembling time. 
Subsequent reloads take just a few milliseconds. After modifying the 
page, reload takes again >4 minutes with full debug.
Most time is spend in ParameterWorker (logs from line 319, 329 and 340).
Another place which takes lot time is Registry (logs from line 67 and 81).

Since the code in ParameterWorker is called some 100.000 or millions 
times, speedup there would bring a big performance plus.

But maybe there are other ways to improve performance?

> There are also a couple of performance tips at the very bottom of
> http://tapestry.apache.org/class-reloading.html
>
> On Mon, Jan 7, 2013 at 10:33 AM, Thiago H de Paula Figueiredo
> <th...@gmail.com> wrote:
>> On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz
>> <mi...@evermind.de> wrote:
>>
>>> Hi,
>>
>> Hi!
>>
>>
>>> we have a big project with Tapestry 5.3. There are many pages, lots of
>>> components and many links between the pages (@Injects of other pages).
>>> The problem is that after a change, the first page reload takes >5 seconds
>>> on good hardware because there is much work for the tapestry page compiler
>>> which wastes much time of our developers.
>>
>> There isn't a Tapestry page compiler, just a template parser and some
>> internal code that creates the page instances. There's no language
>> transformation, so, for me, it isn't compiling at all.
>>
>> The first thing I think you should do is to do some profiling and check
>> whether these 5+ seconds are really all spent in Tapestry internals or if
>> there's some application-specific processing going on (method calls,
>> database queries, etc).
>>
>> --
>> Thiago H. de Paula Figueiredo
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>


-- 
Mit freundlichen Grüßen / Regards

Michael Wyraz

evermind GmbH
Schorlemmerstraße 1
04155 Leipzig

Tel.:       +49 (0)341-25 39 66 - 0
Fax:        +49 (0)341-25 39 66 - 1
Funk:       +49 (0)177-73 00 00 3
E-Mail:     michael.wyraz@evermind.de

HRB: 21586
Amtsgericht Leipzig

Geschäftsführer:
Christoph Klemm
Thomas Grünert
Michael Wyraz


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling

Posted by Bob Harner <bo...@gmail.com>.
There are also a couple of performance tips at the very bottom of
http://tapestry.apache.org/class-reloading.html

On Mon, Jan 7, 2013 at 10:33 AM, Thiago H de Paula Figueiredo
<th...@gmail.com> wrote:
> On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz
> <mi...@evermind.de> wrote:
>
>> Hi,
>
>
> Hi!
>
>
>> we have a big project with Tapestry 5.3. There are many pages, lots of
>> components and many links between the pages (@Injects of other pages).
>> The problem is that after a change, the first page reload takes >5 seconds
>> on good hardware because there is much work for the tapestry page compiler
>> which wastes much time of our developers.
>
>
> There isn't a Tapestry page compiler, just a template parser and some
> internal code that creates the page instances. There's no language
> transformation, so, for me, it isn't compiling at all.
>
> The first thing I think you should do is to do some profiling and check
> whether these 5+ seconds are really all spent in Tapestry internals or if
> there's some application-specific processing going on (method calls,
> database queries, etc).
>
> --
> Thiago H. de Paula Figueiredo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Speed up page compiling

Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz  
<mi...@evermind.de> wrote:

> Hi,

Hi!

> we have a big project with Tapestry 5.3. There are many pages, lots of  
> components and many links between the pages (@Injects of other pages).
> The problem is that after a change, the first page reload takes >5  
> seconds on good hardware because there is much work for the tapestry  
> page compiler which wastes much time of our developers.

There isn't a Tapestry page compiler, just a template parser and some  
internal code that creates the page instances. There's no language  
transformation, so, for me, it isn't compiling at all.

The first thing I think you should do is to do some profiling and check  
whether these 5+ seconds are really all spent in Tapestry internals or if  
there's some application-specific processing going on (method calls,  
database queries, etc).

-- 
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org