You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Thorsten Scherler (JIRA)" <ji...@apache.org> on 2006/01/29 13:31:32 UTC
[jira] Created: (FOR-803) Profile new dispatcher plugins
Profile new dispatcher plugins
------------------------------
Key: FOR-803
URL: http://issues.apache.org/jira/browse/FOR-803
Project: Forrest
Type: Sub-task
Components: Dispatcher (aka views)
Reporter: Thorsten Scherler
http://marc.theaimsgroup.com/?t=113830245600001
El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
A while ago i noticed big performance problems.
> e.g. building site-author took four times as long.
>
> We need to do at least basic profiling.
http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Thorsten Scherler <th...@wyona.com>.
El jue, 09-02-2006 a las 07:08 -0500, Tim Williams escribió:
...
> To both of you... Are these the documented issues or new ones? If
> it's for FOR-732, for development purposes, just turn lm caching off
> in forrest-core.xconf for now.
Well that is the problem, the caching should be configurable in the
sitemap and not the xconf since IMO we should be able to use caching and
non-caching locationmap lookups. *Without* restarting forrest. ;-)
I will add my thoughts and observations to this issue. Thx.
>
> Actually, if I hear no complaints, I'll turn it off by default until
> FOR-732 is resolved.
No, please let it on, but maybe give us some instructions how we can
configure it on a sitemap level (best as <map:pipe/>).
>
> --tim
Thanks Tim.
salu2
--
Thorsten Scherler
COO Spain
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
thorsten.scherler@wyona.com thorsten@apache.org
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Ross Gardler <rg...@apache.org>.
Tim Williams wrote:
> On 2/9/06, Thorsten Scherler <th...@wyona.com> wrote:
...
>>>Unfortunately this means I have to solve some issues with the
>>>locationmap cache first.
>>
>>Yes, I am running ATM as well constantly into caching issues with the
>>locationmap. I thought about a non cached locationmap lookup pipe that
>>will force the locationmap to not use the cache for location lookups.
>
>
> To both of you... Are these the documented issues or new ones? If
> it's for FOR-732, for development purposes, just turn lm caching off
> in forrest-core.xconf for now.
I am not referring to new issues.
> Actually, if I hear no complaints, I'll turn it off by default until
> FOR-732 is resolved.
I'm OK with that, but I need it for this project so my itch is getting
stronger ;-)
Ross
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Tim Williams <wi...@gmail.com>.
On 2/9/06, Thorsten Scherler <th...@wyona.com> wrote:
> El jue, 09-02-2006 a las 10:57 +0000, Ross Gardler escribió:
> > Thorsten Scherler wrote:
> > > El jue, 09-02-2006 a las 18:27 +1100, David Crossley escribió:
> > >
> > >>I started doing some "Cocoon Profiler" on site-author.
> > >>Processing index.html four times then looking at cprofile.html
> > >>
> > >>Compared Dispatcher-enabled site-author with the profile
> > >>of skins-based site-author running on another port.
> > >>
> > >>Still not sure how to interpret results, but
> > >>here are some initial observations.
> > >>
> > >>Using the default theme ...
> > >>
> > >>Some pipelines seem to be requested twice or more
> > >>for each page view, e.g.
> > >>resolve.contract.html.siteinfo-feedback
> > >
> > >
> > > Yes, that is how the dispatcher is working so far. As soon as you use
> > > twice a contract it will be included twice and requested twice.
> >
> > Hmmm.... siteinfo-feedback needs to be called twice because it is used
> > twice. OK - can't avoid that, but we can cache the results in most
> > instances. More below...
>
> Yes, some contracts can be cached others not that easy. Since contracts
> are beans we should take advantages of it. Right now we create on
> instance of the bean and reuse it by this.contract.recycle(); which
> flashes the contract.
>
> Maybe it make more sense to keep different bean instances in a pool
> while processing the request and then if processing ends we flash the
> pool. That makes it possible to look up the bean instance from the pool
> and reuse it if the bean exist in the pool.
>
> The challenge is to have well defined bean identifier since we have to
> keep in mind that if the dataURI is changing we need to set the rawData
> again. Further the contract properties need sometimes as well an update
> of the bean.
>
> >
> > >>Total of about 100 pipelines were processed compared
> > >>with about 45 pipelines for the skins-based site
> > >>and about 40 pipelines for the default dispatcher site.
> > >>
> > >
> > >
> > > The idea is that contracts are standalone and self containing that has
> > > the downside that some information are requested more then once. I am
> > > unsure how we can reuse the pipes more efficient since I reckon they
> > > cause the build time to rise. Maybe we should think about a dispatcher
> > > generator that will request the dataUri and aggregates the data
> > > requested by the structurer. From there we can request this data from
> > > the dispatcher transformer. That would help controlling that contracts
> > > (if using the same dataUri) would use only *one* pool (aggregated by the
> > > dispatcher generator) and the data get requested *only once*.
> > >
> > > wdyt?
> >
> > Eactly what I was thinking...
> >
> > I'm afraid I'm still not able to work on the Dispatcher, however I have
> > a site I am currently working on the back end for and want to use
> > dispatcher on the front end. So as soon as the backend is working
> > sufficiently I will be looking into the dispatcher in detail.
> > Performance is the key for me as the application wil be a dynamic one.
>
> Looking forward to it. ;-)
>
> > Unfortunately this means I have to solve some issues with the
> > locationmap cache first.
>
> Yes, I am running ATM as well constantly into caching issues with the
> locationmap. I thought about a non cached locationmap lookup pipe that
> will force the locationmap to not use the cache for location lookups.
To both of you... Are these the documented issues or new ones? If
it's for FOR-732, for development purposes, just turn lm caching off
in forrest-core.xconf for now.
Actually, if I hear no complaints, I'll turn it off by default until
FOR-732 is resolved.
--tim
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Thorsten Scherler <th...@wyona.com>.
El jue, 09-02-2006 a las 10:57 +0000, Ross Gardler escribió:
> Thorsten Scherler wrote:
> > El jue, 09-02-2006 a las 18:27 +1100, David Crossley escribió:
> >
> >>I started doing some "Cocoon Profiler" on site-author.
> >>Processing index.html four times then looking at cprofile.html
> >>
> >>Compared Dispatcher-enabled site-author with the profile
> >>of skins-based site-author running on another port.
> >>
> >>Still not sure how to interpret results, but
> >>here are some initial observations.
> >>
> >>Using the default theme ...
> >>
> >>Some pipelines seem to be requested twice or more
> >>for each page view, e.g.
> >>resolve.contract.html.siteinfo-feedback
> >
> >
> > Yes, that is how the dispatcher is working so far. As soon as you use
> > twice a contract it will be included twice and requested twice.
>
> Hmmm.... siteinfo-feedback needs to be called twice because it is used
> twice. OK - can't avoid that, but we can cache the results in most
> instances. More below...
Yes, some contracts can be cached others not that easy. Since contracts
are beans we should take advantages of it. Right now we create on
instance of the bean and reuse it by this.contract.recycle(); which
flashes the contract.
Maybe it make more sense to keep different bean instances in a pool
while processing the request and then if processing ends we flash the
pool. That makes it possible to look up the bean instance from the pool
and reuse it if the bean exist in the pool.
The challenge is to have well defined bean identifier since we have to
keep in mind that if the dataURI is changing we need to set the rawData
again. Further the contract properties need sometimes as well an update
of the bean.
>
> >>Total of about 100 pipelines were processed compared
> >>with about 45 pipelines for the skins-based site
> >>and about 40 pipelines for the default dispatcher site.
> >>
> >
> >
> > The idea is that contracts are standalone and self containing that has
> > the downside that some information are requested more then once. I am
> > unsure how we can reuse the pipes more efficient since I reckon they
> > cause the build time to rise. Maybe we should think about a dispatcher
> > generator that will request the dataUri and aggregates the data
> > requested by the structurer. From there we can request this data from
> > the dispatcher transformer. That would help controlling that contracts
> > (if using the same dataUri) would use only *one* pool (aggregated by the
> > dispatcher generator) and the data get requested *only once*.
> >
> > wdyt?
>
> Eactly what I was thinking...
>
> I'm afraid I'm still not able to work on the Dispatcher, however I have
> a site I am currently working on the back end for and want to use
> dispatcher on the front end. So as soon as the backend is working
> sufficiently I will be looking into the dispatcher in detail.
> Performance is the key for me as the application wil be a dynamic one.
Looking forward to it. ;-)
> Unfortunately this means I have to solve some issues with the
> locationmap cache first.
Yes, I am running ATM as well constantly into caching issues with the
locationmap. I thought about a non cached locationmap lookup pipe that
will force the locationmap to not use the cache for location lookups.
salu2
--
Thorsten Scherler
COO Spain
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
thorsten.scherler@wyona.com thorsten@apache.org
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Ross Gardler <rg...@apache.org>.
Thorsten Scherler wrote:
> El jue, 09-02-2006 a las 18:27 +1100, David Crossley escribió:
>
>>I started doing some "Cocoon Profiler" on site-author.
>>Processing index.html four times then looking at cprofile.html
>>
>>Compared Dispatcher-enabled site-author with the profile
>>of skins-based site-author running on another port.
>>
>>Still not sure how to interpret results, but
>>here are some initial observations.
>>
>>Using the default theme ...
>>
>>Some pipelines seem to be requested twice or more
>>for each page view, e.g.
>>resolve.contract.html.siteinfo-feedback
>
>
> Yes, that is how the dispatcher is working so far. As soon as you use
> twice a contract it will be included twice and requested twice.
Hmmm.... siteinfo-feedback needs to be called twice because it is used
twice. OK - can't avoid that, but we can cache the results in most
instances. More below...
>>Total of about 100 pipelines were processed compared
>>with about 45 pipelines for the skins-based site
>>and about 40 pipelines for the default dispatcher site.
>>
>
>
> The idea is that contracts are standalone and self containing that has
> the downside that some information are requested more then once. I am
> unsure how we can reuse the pipes more efficient since I reckon they
> cause the build time to rise. Maybe we should think about a dispatcher
> generator that will request the dataUri and aggregates the data
> requested by the structurer. From there we can request this data from
> the dispatcher transformer. That would help controlling that contracts
> (if using the same dataUri) would use only *one* pool (aggregated by the
> dispatcher generator) and the data get requested *only once*.
>
> wdyt?
Eactly what I was thinking...
I'm afraid I'm still not able to work on the Dispatcher, however I have
a site I am currently working on the back end for and want to use
dispatcher on the front end. So as soon as the backend is working
sufficiently I will be looking into the dispatcher in detail.
Performance is the key for me as the application wil be a dynamic one.
Unfortunately this means I have to solve some issues with the
locationmap cache first.
Ross
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> David Crossley escribi??:
> > I started doing some "Cocoon Profiler" on site-author.
> > Processing index.html four times then looking at cprofile.html
> >
> > Compared Dispatcher-enabled site-author with the profile
> > of skins-based site-author running on another port.
> >
> > Still not sure how to interpret results, but
> > here are some initial observations.
> >
> > Using the default theme ...
> >
> > Some pipelines seem to be requested twice or more
> > for each page view, e.g.
> > resolve.contract.html.siteinfo-feedback
>
> Yes, that is how the dispatcher is working so far. As soon as you use
> twice a contract it will be included twice and requested twice.
>
> > Using the pelt theme ...
> >
> > Seems to process an extra resource called license.html
> > and its associated pieces.
>
> ??? wow, that is a new finding. Thx. No clue ATM why. Which uri did you
> request originally?
See above. I always use index.html and no other requests.
It is also useful to request index.html just one time,
then look at the profiler. Some pipelines are called 25 times.
Need to increase the setting in forrest.core.xconf
To gather further statistics, do index.html four times.
> > Total of about 100 pipelines were processed compared
> > with about 45 pipelines for the skins-based site
> > and about 40 pipelines for the default dispatcher site.
My main query was why are there 100 pipelines using
the pelt theme and only 40 using the default theme?
> The idea is that contracts are standalone and self containing that has
> the downside that some information are requested more then once.
Not so bad if all of the pipelines are cached.
> I am
> unsure how we can reuse the pipes more efficient since I reckon they
> cause the build time to rise. Maybe we should think about a dispatcher
> generator that will request the dataUri and aggregates the data
> requested by the structurer. From there we can request this data from
> the dispatcher transformer. That would help controlling that contracts
> (if using the same dataUri) would use only *one* pool (aggregated by the
> dispatcher generator) and the data get requested *only once*.
Can we still change the data and Forrest would reflect
that change? Rapid application development.
> Thanks David, you are now the official dispatcher "profiler" for me (no
> strings attached). ;-)
I see the smiley, but please, no. We all need to try
to interpet it.
-David
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Thorsten Scherler <th...@wyona.com>.
El jue, 09-02-2006 a las 18:27 +1100, David Crossley escribió:
> I started doing some "Cocoon Profiler" on site-author.
> Processing index.html four times then looking at cprofile.html
>
> Compared Dispatcher-enabled site-author with the profile
> of skins-based site-author running on another port.
>
> Still not sure how to interpret results, but
> here are some initial observations.
>
> Using the default theme ...
>
> Some pipelines seem to be requested twice or more
> for each page view, e.g.
> resolve.contract.html.siteinfo-feedback
Yes, that is how the dispatcher is working so far. As soon as you use
twice a contract it will be included twice and requested twice.
> Using the pelt theme ...
>
> Seems to process an extra resource called license.html
> and its associated pieces.
¿? wow, that is a new finding. Thx. No clue ATM why. Which uri did you
request originally?
>
> Total of about 100 pipelines were processed compared
> with about 45 pipelines for the skins-based site
> and about 40 pipelines for the default dispatcher site.
>
The idea is that contracts are standalone and self containing that has
the downside that some information are requested more then once. I am
unsure how we can reuse the pipes more efficient since I reckon they
cause the build time to rise. Maybe we should think about a dispatcher
generator that will request the dataUri and aggregates the data
requested by the structurer. From there we can request this data from
the dispatcher transformer. That would help controlling that contracts
(if using the same dataUri) would use only *one* pool (aggregated by the
dispatcher generator) and the data get requested *only once*.
wdyt?
> -David
Thanks David, you are now the official dispatcher "profiler" for me (no
strings attached). ;-)
salu2
--
Thorsten Scherler
COO Spain
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
thorsten.scherler@wyona.com thorsten@apache.org
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by David Crossley <cr...@apache.org>.
I started doing some "Cocoon Profiler" on site-author.
Processing index.html four times then looking at cprofile.html
Compared Dispatcher-enabled site-author with the profile
of skins-based site-author running on another port.
Still not sure how to interpret results, but
here are some initial observations.
Using the default theme ...
Some pipelines seem to be requested twice or more
for each page view, e.g.
resolve.contract.html.siteinfo-feedback
Using the pelt theme ...
Seems to process an extra resource called license.html
and its associated pieces.
Total of about 100 pipelines were processed compared
with about 45 pipelines for the skins-based site
and about 40 pipelines for the default dispatcher site.
-David
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Ross Gardler <rg...@apache.org>.
Gavin (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365194 ]
>
> Gavin commented on FOR-803:
> ---------------------------
>
> Using Dispatcher rc1 I can see no performance lags when doing a forrest run,forrest site,forrest -f bot.xml .
> If anything, things are slightly quicker now. It is only a sample site though with few pages so the difference may be more noticable on a larger site. I have no previous records of a site-author build so someone else needs to check that.
Did you do any profiling? If so please post your results to the issue.
Ross
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365194 ]
Gavin commented on FOR-803:
---------------------------
Using Dispatcher rc1 I can see no performance lags when doing a forrest run,forrest site,forrest -f bot.xml .
If anything, things are slightly quicker now. It is only a sample site though with few pages so the difference may be more noticable on a larger site. I have no previous records of a site-author build so someone else needs to check that.
Gav...
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365526 ]
David Crossley commented on FOR-803:
------------------------------------
cd forrest/site-author
date; forrest site; date
2006-02-08 SVN r375852
417 docs
------
Using pelt skin
Wall clock: 4m 19s
------
Using pelt theme
Note: still has "xml doc" output too, so generating extra 71 files at approximately 0.05s each (= 3.5s)
Wall clock: 6m 34s
------
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12366098 ]
Thorsten Scherler commented on FOR-803:
---------------------------------------
Since I fixed FOR-807 we can now repeat the testing (I think it is actually getting faster)
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12366187 ]
David Crossley commented on FOR-803:
------------------------------------
Time to build the whole site-author ...
2006-02-13 SVN r377271
417 docs
Before starting, do 'build clean' etc. Run forrest once to get all of the plugins deployed.
[localhost]$ cd forrest/site-author
Make the relevant changes to forrest.properties and do 'forrest clean'.
[localhost]$ time forrest site
Do five builds for each situation.
The numbers are total time followed by the amount of system time in brackets.
The "average" excludes the first build.
Not sure why the first build takes longer. Perhaps the cache is being used on the subsequent builds.
------
Using pelt skin ...
4m13s (15.8s), 3m01s (9.2s), 2m56s (9.2s), 2m54s (9.5s), 2m58s (9.2s)
average: 2m57s (9.3s)
Using default theme ...
6m29s 24.3s, 5m29s (19.3s), 5m23s (18.9s), 5m 30s (19.0s), 5m 32s (18.9s)
average: 5m28s (19.0s)
Using pelt theme ...
8m20s (30.6s) 7m05s (24.9), 7m13s (24.8s), 7m20s (25.6), 6m59s (25.0)
average:
------
Note: Dispatcher themes still have "xml doc" output too, so generating extra 157 files at approximately 0.05s each (= 8s)
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (FOR-803) Profile new dispatcher
plugins
Posted by "Brian M Dube (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617230#action_12617230 ]
brian edited comment on FOR-803 at 7/27/08 9:25 AM:
-----------------------------------------------------------
The following output is generated while rendering one page in dynamic mode, /blog/index.html.
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select this_.ID as ID48_0_, this_.post_author as post2_48_0_, this_.post_date as post3_48_0_, this_.post_date_gmt as post4_48_0_, this_.post_content as post5_48_0_, this_.post_title as post6_48_0_, this_.post_category as post7_48_0_, this_.post_excerpt as post8_48_0_, this_.post_status as post9_48_0_, this_.comment_status as comment10_48_0_, this_.ping_status as ping11_48_0_, this_.post_password as post12_48_0_, this_.post_name as post13_48_0_, this_.to_ping as to14_48_0_, this_.pinged as pinged48_0_, this_.post_modified as post16_48_0_, this_.post_modified_gmt as post17_48_0_, this_.post_content_filtered as post18_48_0_, this_.post_parent as post19_48_0_, this_.guid as guid48_0_, this_.menu_order as menu21_48_0_, this_.post_type as post22_48_0_, this_.post_mime_type as post23_48_0_, this_.comment_count as comment24_48_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID54_0_, this_.post_author as post2_54_0_, this_.post_date as post3_54_0_, this_.post_date_gmt as post4_54_0_, this_.post_content as post5_54_0_, this_.post_title as post6_54_0_, this_.post_category as post7_54_0_, this_.post_excerpt as post8_54_0_, this_.post_status as post9_54_0_, this_.comment_status as comment10_54_0_, this_.ping_status as ping11_54_0_, this_.post_password as post12_54_0_, this_.post_name as post13_54_0_, this_.to_ping as to14_54_0_, this_.pinged as pinged54_0_, this_.post_modified as post16_54_0_, this_.post_modified_gmt as post17_54_0_, this_.post_content_filtered as post18_54_0_, this_.post_parent as post19_54_0_, this_.guid as guid54_0_, this_.menu_order as menu21_54_0_, this_.post_type as post22_54_0_, this_.post_mime_type as post23_54_0_, this_.comment_count as comment24_54_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID60_0_, this_.post_author as post2_60_0_, this_.post_date as post3_60_0_, this_.post_date_gmt as post4_60_0_, this_.post_content as post5_60_0_, this_.post_title as post6_60_0_, this_.post_category as post7_60_0_, this_.post_excerpt as post8_60_0_, this_.post_status as post9_60_0_, this_.comment_status as comment10_60_0_, this_.ping_status as ping11_60_0_, this_.post_password as post12_60_0_, this_.post_name as post13_60_0_, this_.to_ping as to14_60_0_, this_.pinged as pinged60_0_, this_.post_modified as post16_60_0_, this_.post_modified_gmt as post17_60_0_, this_.post_content_filtered as post18_60_0_, this_.post_parent as post19_60_0_, this_.guid as guid60_0_, this_.menu_order as menu21_60_0_, this_.post_type as post22_60_0_, this_.post_mime_type as post23_60_0_, this_.comment_count as comment24_60_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID66_0_, this_.post_author as post2_66_0_, this_.post_date as post3_66_0_, this_.post_date_gmt as post4_66_0_, this_.post_content as post5_66_0_, this_.post_title as post6_66_0_, this_.post_category as post7_66_0_, this_.post_excerpt as post8_66_0_, this_.post_status as post9_66_0_, this_.comment_status as comment10_66_0_, this_.ping_status as ping11_66_0_, this_.post_password as post12_66_0_, this_.post_name as post13_66_0_, this_.to_ping as to14_66_0_, this_.pinged as pinged66_0_, this_.post_modified as post16_66_0_, this_.post_modified_gmt as post17_66_0_, this_.post_content_filtered as post18_66_0_, this_.post_parent as post19_66_0_, this_.guid as guid66_0_, this_.menu_order as menu21_66_0_, this_.post_type as post22_66_0_, this_.post_mime_type as post23_66_0_, this_.comment_count as comment24_66_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID72_0_, this_.post_author as post2_72_0_, this_.post_date as post3_72_0_, this_.post_date_gmt as post4_72_0_, this_.post_content as post5_72_0_, this_.post_title as post6_72_0_, this_.post_category as post7_72_0_, this_.post_excerpt as post8_72_0_, this_.post_status as post9_72_0_, this_.comment_status as comment10_72_0_, this_.ping_status as ping11_72_0_, this_.post_password as post12_72_0_, this_.post_name as post13_72_0_, this_.to_ping as to14_72_0_, this_.pinged as pinged72_0_, this_.post_modified as post16_72_0_, this_.post_modified_gmt as post17_72_0_, this_.post_content_filtered as post18_72_0_, this_.post_parent as post19_72_0_, this_.guid as guid72_0_, this_.menu_order as menu21_72_0_, this_.post_type as post22_72_0_, this_.post_mime_type as post23_72_0_, this_.comment_count as comment24_72_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID78_0_, this_.post_author as post2_78_0_, this_.post_date as post3_78_0_, this_.post_date_gmt as post4_78_0_, this_.post_content as post5_78_0_, this_.post_title as post6_78_0_, this_.post_category as post7_78_0_, this_.post_excerpt as post8_78_0_, this_.post_status as post9_78_0_, this_.comment_status as comment10_78_0_, this_.ping_status as ping11_78_0_, this_.post_password as post12_78_0_, this_.post_name as post13_78_0_, this_.to_ping as to14_78_0_, this_.pinged as pinged78_0_, this_.post_modified as post16_78_0_, this_.post_modified_gmt as post17_78_0_, this_.post_content_filtered as post18_78_0_, this_.post_parent as post19_78_0_, this_.guid as guid78_0_, this_.menu_order as menu21_78_0_, this_.post_type as post22_78_0_, this_.post_mime_type as post23_78_0_, this_.comment_count as comment24_78_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID84_0_, this_.post_author as post2_84_0_, this_.post_date as post3_84_0_, this_.post_date_gmt as post4_84_0_, this_.post_content as post5_84_0_, this_.post_title as post6_84_0_, this_.post_category as post7_84_0_, this_.post_excerpt as post8_84_0_, this_.post_status as post9_84_0_, this_.comment_status as comment10_84_0_, this_.ping_status as ping11_84_0_, this_.post_password as post12_84_0_, this_.post_name as post13_84_0_, this_.to_ping as to14_84_0_, this_.pinged as pinged84_0_, this_.post_modified as post16_84_0_, this_.post_modified_gmt as post17_84_0_, this_.post_content_filtered as post18_84_0_, this_.post_parent as post19_84_0_, this_.guid as guid84_0_, this_.menu_order as menu21_84_0_, this_.post_type as post22_84_0_, this_.post_mime_type as post23_84_0_, this_.comment_count as comment24_84_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID90_0_, this_.post_author as post2_90_0_, this_.post_date as post3_90_0_, this_.post_date_gmt as post4_90_0_, this_.post_content as post5_90_0_, this_.post_title as post6_90_0_, this_.post_category as post7_90_0_, this_.post_excerpt as post8_90_0_, this_.post_status as post9_90_0_, this_.comment_status as comment10_90_0_, this_.ping_status as ping11_90_0_, this_.post_password as post12_90_0_, this_.post_name as post13_90_0_, this_.to_ping as to14_90_0_, this_.pinged as pinged90_0_, this_.post_modified as post16_90_0_, this_.post_modified_gmt as post17_90_0_, this_.post_content_filtered as post18_90_0_, this_.post_parent as post19_90_0_, this_.guid as guid90_0_, this_.menu_order as menu21_90_0_, this_.post_type as post22_90_0_, this_.post_mime_type as post23_90_0_, this_.comment_count as comment24_90_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID96_0_, this_.post_author as post2_96_0_, this_.post_date as post3_96_0_, this_.post_date_gmt as post4_96_0_, this_.post_content as post5_96_0_, this_.post_title as post6_96_0_, this_.post_category as post7_96_0_, this_.post_excerpt as post8_96_0_, this_.post_status as post9_96_0_, this_.comment_status as comment10_96_0_, this_.ping_status as ping11_96_0_, this_.post_password as post12_96_0_, this_.post_name as post13_96_0_, this_.to_ping as to14_96_0_, this_.pinged as pinged96_0_, this_.post_modified as post16_96_0_, this_.post_modified_gmt as post17_96_0_, this_.post_content_filtered as post18_96_0_, this_.post_parent as post19_96_0_, this_.guid as guid96_0_, this_.menu_order as menu21_96_0_, this_.post_type as post22_96_0_, this_.post_mime_type as post23_96_0_, this_.comment_count as comment24_96_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID102_0_, this_.post_author as post2_102_0_, this_.post_date as post3_102_0_, this_.post_date_gmt as post4_102_0_, this_.post_content as post5_102_0_, this_.post_title as post6_102_0_, this_.post_category as post7_102_0_, this_.post_excerpt as post8_102_0_, this_.post_status as post9_102_0_, this_.comment_status as comment10_102_0_, this_.ping_status as ping11_102_0_, this_.post_password as post12_102_0_, this_.post_name as post13_102_0_, this_.to_ping as to14_102_0_, this_.pinged as pinged102_0_, this_.post_modified as post16_102_0_, this_.post_modified_gmt as post17_102_0_, this_.post_content_filtered as post18_102_0_, this_.post_parent as post19_102_0_, this_.guid as guid102_0_, this_.menu_order as menu21_102_0_, this_.post_type as post22_102_0_, this_.post_mime_type as post23_102_0_, this_.comment_count as comment24_102_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
19:00:33.842 WARN!! GET /blog/category/uncategorized/index.html HTTP/1.1
java.lang.OutOfMemoryError: Java heap space
at java.util.jar.Manifest$FastInputStream.<init>(Manifest.java:300)
at java.util.jar.Manifest$FastInputStream.<init>(Manifest.java:295)
at java.util.jar.Manifest.read(Manifest.java:163)
at java.util.jar.Manifest.<init>(Manifest.java:52)
at java.util.jar.JarFile.getManifestFromReference(JarFile.java:163)
at java.util.jar.JarFile.getManifest(JarFile.java:145)
at sun.misc.URLClassPath$JarLoader$1.getManifest(URLClassPath.java:624)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:221)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at org.mortbay.util.Code.warning(Code.java:384)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:609)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1808)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1758)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:952)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:197)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:501)
was (Author: brian):
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select this_.ID as ID48_0_, this_.post_author as post2_48_0_, this_.post_date as post3_48_0_, this_.post_date_gmt as post4_48_0_, this_.post_content as post5_48_0_, this_.post_title as post6_48_0_, this_.post_category as post7_48_0_, this_.post_excerpt as post8_48_0_, this_.post_status as post9_48_0_, this_.comment_status as comment10_48_0_, this_.ping_status as ping11_48_0_, this_.post_password as post12_48_0_, this_.post_name as post13_48_0_, this_.to_ping as to14_48_0_, this_.pinged as pinged48_0_, this_.post_modified as post16_48_0_, this_.post_modified_gmt as post17_48_0_, this_.post_content_filtered as post18_48_0_, this_.post_parent as post19_48_0_, this_.guid as guid48_0_, this_.menu_order as menu21_48_0_, this_.post_type as post22_48_0_, this_.post_mime_type as post23_48_0_, this_.comment_count as comment24_48_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID54_0_, this_.post_author as post2_54_0_, this_.post_date as post3_54_0_, this_.post_date_gmt as post4_54_0_, this_.post_content as post5_54_0_, this_.post_title as post6_54_0_, this_.post_category as post7_54_0_, this_.post_excerpt as post8_54_0_, this_.post_status as post9_54_0_, this_.comment_status as comment10_54_0_, this_.ping_status as ping11_54_0_, this_.post_password as post12_54_0_, this_.post_name as post13_54_0_, this_.to_ping as to14_54_0_, this_.pinged as pinged54_0_, this_.post_modified as post16_54_0_, this_.post_modified_gmt as post17_54_0_, this_.post_content_filtered as post18_54_0_, this_.post_parent as post19_54_0_, this_.guid as guid54_0_, this_.menu_order as menu21_54_0_, this_.post_type as post22_54_0_, this_.post_mime_type as post23_54_0_, this_.comment_count as comment24_54_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID60_0_, this_.post_author as post2_60_0_, this_.post_date as post3_60_0_, this_.post_date_gmt as post4_60_0_, this_.post_content as post5_60_0_, this_.post_title as post6_60_0_, this_.post_category as post7_60_0_, this_.post_excerpt as post8_60_0_, this_.post_status as post9_60_0_, this_.comment_status as comment10_60_0_, this_.ping_status as ping11_60_0_, this_.post_password as post12_60_0_, this_.post_name as post13_60_0_, this_.to_ping as to14_60_0_, this_.pinged as pinged60_0_, this_.post_modified as post16_60_0_, this_.post_modified_gmt as post17_60_0_, this_.post_content_filtered as post18_60_0_, this_.post_parent as post19_60_0_, this_.guid as guid60_0_, this_.menu_order as menu21_60_0_, this_.post_type as post22_60_0_, this_.post_mime_type as post23_60_0_, this_.comment_count as comment24_60_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID66_0_, this_.post_author as post2_66_0_, this_.post_date as post3_66_0_, this_.post_date_gmt as post4_66_0_, this_.post_content as post5_66_0_, this_.post_title as post6_66_0_, this_.post_category as post7_66_0_, this_.post_excerpt as post8_66_0_, this_.post_status as post9_66_0_, this_.comment_status as comment10_66_0_, this_.ping_status as ping11_66_0_, this_.post_password as post12_66_0_, this_.post_name as post13_66_0_, this_.to_ping as to14_66_0_, this_.pinged as pinged66_0_, this_.post_modified as post16_66_0_, this_.post_modified_gmt as post17_66_0_, this_.post_content_filtered as post18_66_0_, this_.post_parent as post19_66_0_, this_.guid as guid66_0_, this_.menu_order as menu21_66_0_, this_.post_type as post22_66_0_, this_.post_mime_type as post23_66_0_, this_.comment_count as comment24_66_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID72_0_, this_.post_author as post2_72_0_, this_.post_date as post3_72_0_, this_.post_date_gmt as post4_72_0_, this_.post_content as post5_72_0_, this_.post_title as post6_72_0_, this_.post_category as post7_72_0_, this_.post_excerpt as post8_72_0_, this_.post_status as post9_72_0_, this_.comment_status as comment10_72_0_, this_.ping_status as ping11_72_0_, this_.post_password as post12_72_0_, this_.post_name as post13_72_0_, this_.to_ping as to14_72_0_, this_.pinged as pinged72_0_, this_.post_modified as post16_72_0_, this_.post_modified_gmt as post17_72_0_, this_.post_content_filtered as post18_72_0_, this_.post_parent as post19_72_0_, this_.guid as guid72_0_, this_.menu_order as menu21_72_0_, this_.post_type as post22_72_0_, this_.post_mime_type as post23_72_0_, this_.comment_count as comment24_72_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID78_0_, this_.post_author as post2_78_0_, this_.post_date as post3_78_0_, this_.post_date_gmt as post4_78_0_, this_.post_content as post5_78_0_, this_.post_title as post6_78_0_, this_.post_category as post7_78_0_, this_.post_excerpt as post8_78_0_, this_.post_status as post9_78_0_, this_.comment_status as comment10_78_0_, this_.ping_status as ping11_78_0_, this_.post_password as post12_78_0_, this_.post_name as post13_78_0_, this_.to_ping as to14_78_0_, this_.pinged as pinged78_0_, this_.post_modified as post16_78_0_, this_.post_modified_gmt as post17_78_0_, this_.post_content_filtered as post18_78_0_, this_.post_parent as post19_78_0_, this_.guid as guid78_0_, this_.menu_order as menu21_78_0_, this_.post_type as post22_78_0_, this_.post_mime_type as post23_78_0_, this_.comment_count as comment24_78_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID84_0_, this_.post_author as post2_84_0_, this_.post_date as post3_84_0_, this_.post_date_gmt as post4_84_0_, this_.post_content as post5_84_0_, this_.post_title as post6_84_0_, this_.post_category as post7_84_0_, this_.post_excerpt as post8_84_0_, this_.post_status as post9_84_0_, this_.comment_status as comment10_84_0_, this_.ping_status as ping11_84_0_, this_.post_password as post12_84_0_, this_.post_name as post13_84_0_, this_.to_ping as to14_84_0_, this_.pinged as pinged84_0_, this_.post_modified as post16_84_0_, this_.post_modified_gmt as post17_84_0_, this_.post_content_filtered as post18_84_0_, this_.post_parent as post19_84_0_, this_.guid as guid84_0_, this_.menu_order as menu21_84_0_, this_.post_type as post22_84_0_, this_.post_mime_type as post23_84_0_, this_.comment_count as comment24_84_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID90_0_, this_.post_author as post2_90_0_, this_.post_date as post3_90_0_, this_.post_date_gmt as post4_90_0_, this_.post_content as post5_90_0_, this_.post_title as post6_90_0_, this_.post_category as post7_90_0_, this_.post_excerpt as post8_90_0_, this_.post_status as post9_90_0_, this_.comment_status as comment10_90_0_, this_.ping_status as ping11_90_0_, this_.post_password as post12_90_0_, this_.post_name as post13_90_0_, this_.to_ping as to14_90_0_, this_.pinged as pinged90_0_, this_.post_modified as post16_90_0_, this_.post_modified_gmt as post17_90_0_, this_.post_content_filtered as post18_90_0_, this_.post_parent as post19_90_0_, this_.guid as guid90_0_, this_.menu_order as menu21_90_0_, this_.post_type as post22_90_0_, this_.post_mime_type as post23_90_0_, this_.comment_count as comment24_90_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID96_0_, this_.post_author as post2_96_0_, this_.post_date as post3_96_0_, this_.post_date_gmt as post4_96_0_, this_.post_content as post5_96_0_, this_.post_title as post6_96_0_, this_.post_category as post7_96_0_, this_.post_excerpt as post8_96_0_, this_.post_status as post9_96_0_, this_.comment_status as comment10_96_0_, this_.ping_status as ping11_96_0_, this_.post_password as post12_96_0_, this_.post_name as post13_96_0_, this_.to_ping as to14_96_0_, this_.pinged as pinged96_0_, this_.post_modified as post16_96_0_, this_.post_modified_gmt as post17_96_0_, this_.post_content_filtered as post18_96_0_, this_.post_parent as post19_96_0_, this_.guid as guid96_0_, this_.menu_order as menu21_96_0_, this_.post_type as post22_96_0_, this_.post_mime_type as post23_96_0_, this_.comment_count as comment24_96_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID102_0_, this_.post_author as post2_102_0_, this_.post_date as post3_102_0_, this_.post_date_gmt as post4_102_0_, this_.post_content as post5_102_0_, this_.post_title as post6_102_0_, this_.post_category as post7_102_0_, this_.post_excerpt as post8_102_0_, this_.post_status as post9_102_0_, this_.comment_status as comment10_102_0_, this_.ping_status as ping11_102_0_, this_.post_password as post12_102_0_, this_.post_name as post13_102_0_, this_.to_ping as to14_102_0_, this_.pinged as pinged102_0_, this_.post_modified as post16_102_0_, this_.post_modified_gmt as post17_102_0_, this_.post_content_filtered as post18_102_0_, this_.post_parent as post19_102_0_, this_.guid as guid102_0_, this_.menu_order as menu21_102_0_, this_.post_type as post22_102_0_, this_.post_mime_type as post23_102_0_, this_.comment_count as comment24_102_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
19:00:33.842 WARN!! GET /blog/category/uncategorized/index.html HTTP/1.1
java.lang.OutOfMemoryError: Java heap space
at java.util.jar.Manifest$FastInputStream.<init>(Manifest.java:300)
at java.util.jar.Manifest$FastInputStream.<init>(Manifest.java:295)
at java.util.jar.Manifest.read(Manifest.java:163)
at java.util.jar.Manifest.<init>(Manifest.java:52)
at java.util.jar.JarFile.getManifestFromReference(JarFile.java:163)
at java.util.jar.JarFile.getManifest(JarFile.java:145)
at sun.misc.URLClassPath$JarLoader$1.getManifest(URLClassPath.java:624)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:221)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at org.mortbay.util.Code.warning(Code.java:384)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:609)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1808)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1758)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:952)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:197)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:501)
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: https://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Issue Type: Sub-task
> Components: Plugin: internal.dispatcher
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commenté: (FOR-803) Profile new dispatcher plugins
Posted by "Cyriaque Dupoirieux (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365553 ]
Cyriaque Dupoirieux commented on FOR-803:
-----------------------------------------
time command is better to make such a test :
$ cd forrest/site-author
$ time forrest site
I am not currently working on forrest so I cannot give you the result ;-)
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (FOR-803) Profile new dispatcher plugins
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=all ]
David Crossley updated FOR-803:
-------------------------------
Comment: was deleted
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (FOR-803) Profile new dispatcher plugins
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=all ]
David Crossley updated FOR-803:
-------------------------------
Comment: was deleted
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Brian M Dube <bd...@apache.org>.
Thorsten Scherler wrote:
> On Sun, 2008-07-20 at 22:51 -0700, Brian M Dube (JIRA) wrote:
>> [ https://issues.apache.org/jira/browse/FOR-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615152#action_12615152 ]
>>
>> Brian M Dube commented on FOR-803:
>> ----------------------------------
>>
>> I'm developing a plugin that uses Hibernate ORM capabilities, and I have Hibernate configured to display its SQL statements as it hits the database while I test. With the pelt skin, the database is hit a few times and the page finishes rendering.
>
> Actually I reckon it should be one match not more. What are the matches?
What matches are you talking about? I'm talking about SQL statements,
and in this case it takes more than one SQL statement to retrieve the
data for the page.
>> With the pelt theme, the database is hit over and over again for the same information before rendering the page.
>
> That indicates a bug in the data-source plugins (if catching is enabled
> the cache should return the hit and not pass it through the db plugin).
Where is dispatcher caching controlled?
>> Navigating to another page will eventually use up all of the heap space and the JVM will hang. I increased the amount of memory available to the JVM, and the connection pool ran out of connections.
>
> Can you please fill a stacktrace to which parts are requested twice, we
> need to find out where the caching is failing.
I've added it to the issue now.
Brian
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Brian M Dube <bd...@apache.org>.
Thorsten Scherler wrote:
> On Sat, 2008-07-26 at 19:04 -0700, Brian M Dube wrote:
>> Where is dispatcher caching controlled?
>
> The dispatcher has multiple tier of caching due to the architecture.
>
> The main pipeline has first the jx pages (see e.g. common.fv):
> jx:cache-key="#{$cocoon/parameters/getRequest}"
> jx:cache-validity="${Packages.org.apache.excalibur.source.impl.validity.NOPValidity()}"
>
> Then the dispatcher transformer as well is cacheable via the "normal"
> cocoon mechanism (getKey() & getValidity()). You can deactivate the
> caching of the transformer by changing <property
> name="dispatcher.caching" value="on" />.
Ok, it seems that I need to reconfigure to make use of the cache. I've
changed my plugin's generators to implement
CacheableProcessingComponent, but I see in the logs that the cache is
not being used. The cache is checking for the existence of a file based
on the sitemap match, but there is no file there because the match is
only a placeholder for data coming from the database. I'm afraid it's my
lack of Cocoon knowledge that's hurting me here.
>>>> Navigating to another page will eventually use up all of the heap space and the JVM will hang. I increased the amount of memory available to the JVM, and the connection pool ran out of connections.
>>> Can you please fill a stacktrace to which parts are requested twice, we
>>> need to find out where the caching is failing.
>> I've added it to the issue now.
>
> Hmm, lots of sql but we need to see as well the requested url and the
> sitemap matches provoking the statements (best as well the structurer
> you use).
I'd like to put the plugin in the whiteboard, but it has some
dependencies that we can't distribute. Perhaps it should be hosted
elsewhere, like the SourceForge project that Ross has set up for plugins.
Thanks for the help, Thorsten.
Brian
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
On Sat, 2008-07-26 at 19:04 -0700, Brian M Dube wrote:
> Thorsten Scherler wrote:
> > On Sun, 2008-07-20 at 22:51 -0700, Brian M Dube (JIRA) wrote:
> >> [ https://issues.apache.org/jira/browse/FOR-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615152#action_12615152 ]
> >>
> >> Brian M Dube commented on FOR-803:
> >> ----------------------------------
> >>
> >> I'm developing a plugin that uses Hibernate ORM capabilities, and I have Hibernate configured to display its SQL statements as it hits the database while I test. With the pelt skin, the database is hit a few times and the page finishes rendering.
> >
> > Actually I reckon it should be one match not more. What are the matches?
>
> What matches are you talking about? I'm talking about SQL statements,
> and in this case it takes more than one SQL statement to retrieve the
> data for the page.
I am talking about matches in cocoon. I imaging that the plugin will
expose the data from the db via sitemap matches. This matches should be
cacheable that cocoon will answer multiple request to the same match.
In dispatcher we call this dataModel or connector since it producing the
raw xml data which will then be used in the contracts.
>
> >> With the pelt theme, the database is hit over and over again for the same information before rendering the page.
> >
> > That indicates a bug in the data-source plugins (if catching is enabled
> > the cache should return the hit and not pass it through the db plugin).
>
> Where is dispatcher caching controlled?
The dispatcher has multiple tier of caching due to the architecture.
The main pipeline has first the jx pages (see e.g. common.fv):
jx:cache-key="#{$cocoon/parameters/getRequest}"
jx:cache-validity="${Packages.org.apache.excalibur.source.impl.validity.NOPValidity()}"
Then the dispatcher transformer as well is cacheable via the "normal"
cocoon mechanism (getKey() & getValidity()). You can deactivate the
caching of the transformer by changing <property
name="dispatcher.caching" value="on" />.
Now since the idea is that the structurer is the configuration for the
dispatcher (as front end controller) each contract you use can be
injected with your dataUri and the resulting xml will be transformed
with the contracts xsl.
If you see lots of request to one and the same data source then this
datasource should be chached.
>
> >> Navigating to another page will eventually use up all of the heap space and the JVM will hang. I increased the amount of memory available to the JVM, and the connection pool ran out of connections.
> >
> > Can you please fill a stacktrace to which parts are requested twice, we
> > need to find out where the caching is failing.
>
> I've added it to the issue now.
Hmm, lots of sql but we need to see as well the requested url and the
sitemap matches provoking the statements (best as well the structurer
you use).
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Brian M Dube <br...@gmail.com>.
Thorsten Scherler wrote:
> On Sun, 2008-07-20 at 22:51 -0700, Brian M Dube (JIRA) wrote:
>> [ https://issues.apache.org/jira/browse/FOR-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615152#action_12615152 ]
>>
>> Brian M Dube commented on FOR-803:
>> ----------------------------------
>>
>> I'm developing a plugin that uses Hibernate ORM capabilities, and I have Hibernate configured to display its SQL statements as it hits the database while I test. With the pelt skin, the database is hit a few times and the page finishes rendering.
>
> Actually I reckon it should be one match not more. What are the matches?
What matches are you talking about? I'm talking about SQL statements,
and in this case it takes more than one SQL statement to retrieve the
data for the page.
>> With the pelt theme, the database is hit over and over again for the same information before rendering the page.
>
> That indicates a bug in the data-source plugins (if catching is enabled
> the cache should return the hit and not pass it through the db plugin).
Where is dispatcher caching controlled?
>> Navigating to another page will eventually use up all of the heap space and the JVM will hang. I increased the amount of memory available to the JVM, and the connection pool ran out of connections.
>
> Can you please fill a stacktrace to which parts are requested twice, we
> need to find out where the caching is failing.
I've added it to the issue now.
Brian
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Thorsten Scherler <th...@apache.org>.
On Sun, 2008-07-20 at 22:51 -0700, Brian M Dube (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/FOR-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615152#action_12615152 ]
>
> Brian M Dube commented on FOR-803:
> ----------------------------------
>
> I'm developing a plugin that uses Hibernate ORM capabilities, and I have Hibernate configured to display its SQL statements as it hits the database while I test. With the pelt skin, the database is hit a few times and the page finishes rendering.
Actually I reckon it should be one match not more. What are the matches?
> With the pelt theme, the database is hit over and over again for the same information before rendering the page.
That indicates a bug in the data-source plugins (if catching is enabled
the cache should return the hit and not pass it through the db plugin).
> Navigating to another page will eventually use up all of the heap space and the JVM will hang. I increased the amount of memory available to the JVM, and the connection pool ran out of connections.
Can you please fill a stacktrace to which parts are requested twice, we
need to find out where the caching is failing.
TIA
salu2
>
> > Profile new dispatcher plugins
> > ------------------------------
> >
> > Key: FOR-803
> > URL: https://issues.apache.org/jira/browse/FOR-803
> > Project: Forrest
> > Issue Type: Sub-task
> > Components: Plugin: internal.dispatcher
> > Reporter: Thorsten Scherler
> >
> > http://marc.theaimsgroup.com/?t=113830245600001
> > El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> > A while ago i noticed big performance problems.
> > > e.g. building site-author took four times as long.
> > >
> > > We need to do at least basic profiling.
> > http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> > David was talking about v2 but this needs to be verified with the refactored version.
>
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "Brian M Dube (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615152#action_12615152 ]
Brian M Dube commented on FOR-803:
----------------------------------
I'm developing a plugin that uses Hibernate ORM capabilities, and I have Hibernate configured to display its SQL statements as it hits the database while I test. With the pelt skin, the database is hit a few times and the page finishes rendering. With the pelt theme, the database is hit over and over again for the same information before rendering the page. Navigating to another page will eventually use up all of the heap space and the JVM will hang. I increased the amount of memory available to the JVM, and the connection pool ran out of connections.
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: https://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Issue Type: Sub-task
> Components: Plugin: internal.dispatcher
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365656 ]
Thorsten Scherler commented on FOR-803:
---------------------------------------
Thx David for the test data. :)
NOTE: When the test have been done the site-author seed was not builded succefully, which has influnce on the build time (I reckon it will go a wee bit up). We should repeat the site-author test when FOR-807 is closed.
The dispatcher seems to be better regarding performance in comparison with the old "views" but in comparison to skins there is still a lot of improvement.
Like pointed out in
http://marc.theaimsgroup.com/?t=113273973400004&r=1&w=2 current ContratBean implementation and DispatcherTransformer is based on DOM.
Alternative implemetations should be based on StAX, mentioned in
http://marc.theaimsgroup.com/?t=113405136000003&r=1&w=2
Further we may consider to make the DispatcherTransformer cacheable.
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (FOR-803) Profile new dispatcher plugins
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=all ]
David Crossley updated FOR-803:
-------------------------------
Comment: was deleted
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12366190 ]
David Crossley commented on FOR-803:
------------------------------------
Time to build the whole site-author
2006-02-13 SVN r377271
417 docs
Before starting, do 'build clean' etc. Run forrest once to get all of the plugins deployed.
[localhost]$ cd forrest/site-author
Make the relevant changes to forrest.properties and do 'forrest clean'.
[localhost]$ time forrest site
Do five builds for each situation.
The numbers are total time followed by the amount of system time in brackets.
The "average" excludes the first build.
Not sure why the first build takes longer. Perhaps the cache is being used on the subsequent builds.
------
Using pelt skin ...
4m13s (15.8s), 3m01s (9.2s), 2m56s (9.2s), 2m54s (9.5s), 2m58s (9.2s)
average: 2m57s (9.3s)
Using default theme ...
6m29s 24.3s, 5m29s (19.3s), 5m23s (18.9s), 5m 30s (19.0s), 5m 32s (18.9s)
average: 5m28s (19.0s)
Using pelt theme ...
8m20s (30.6s) 7m05s (24.9), 7m13s (24.8s), 7m20s (25.6), 6m59s (25.0)
average: 7m09s (25.1s)
------
Note: Dispatcher themes still have "xml doc" output too, so generating extra 157 files at approximately 0.05s each (= 8s)
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365531 ]
David Crossley commented on FOR-803:
------------------------------------
Startup times for 'forrest run'
2006-02-08 SVN r375852
date; forrest run
... when ready, do localhost:8888/index.html
date when see "Done" in browser.
Average of four runs each.
------
Using pelt skin ... Wall clock: 23s
Using default theme ... Wall clock: 28s
Using pelt theme ... Wall clock: 31s
------
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12366189 ]
David Crossley commented on FOR-803:
------------------------------------
Startup times for 'forrest run'
2006-02-13 SVN r377271
date; forrest run
... when ready, do localhost:8888/index.html
date when see "Done" in browser.
Average of four runs each. Did 'forrest clean' between each theme switch.
------
Using pelt skin ... 24s
Using default theme ... 26s
Using pelt theme ... 30s
------
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365532 ]
David Crossley commented on FOR-803:
------------------------------------
Time to build the whole site-author
cd forrest/site-author
date; forrest site; date
2006-02-08 SVN r375852
417 docs
Did average of four builds each.
------
Using pelt skin ... Wall clock: 4m 00s
Using default theme ... Wall clock: 6m 30s
Using pelt theme ... Wall clock: 8m 10s
------
Note: Dispatcher themes still have "xml doc" output too, so generating extra 157 files at approximately 0.05s each (= 8s)
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by Thorsten Scherler <th...@apache.org>.
El mié, 08-02-2006 a las 08:15 +0100, David Crossley (JIRA) escribió:
> [ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365529 ]
>
> David Crossley commented on FOR-803:
> ------------------------------------
>
> cd forrest/site-author
> date; forrest site; date
>
> 2006-02-08 SVN r375852
> 417 docs
>
> Did average of four builds each.
>
> ------
> Using pelt skin ... Wall clock: 4m 19s
> Using default theme ... Wall clock: 6m 30s
> Using pelt theme ... Wall clock: 8m 10s
> ------
>
> Note: Dispatcher themes still have "xml doc" output too, so generating extra 157 files at approximately 0.05s each (= 8s)
>
...and http://issues.apache.org/jira/browse/FOR-807
The site-author is (till now) not generated correctly this is
influencing the result.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365529 ]
David Crossley commented on FOR-803:
------------------------------------
cd forrest/site-author
date; forrest site; date
2006-02-08 SVN r375852
417 docs
Did average of four builds each.
------
Using pelt skin ... Wall clock: 4m 19s
Using default theme ... Wall clock: 6m 30s
Using pelt theme ... Wall clock: 8m 10s
------
Note: Dispatcher themes still have "xml doc" output too, so generating extra 157 files at approximately 0.05s each (= 8s)
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: http://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Type: Sub-task
> Components: Dispatcher (aka views)
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-803) Profile new dispatcher plugins
Posted by "Brian M Dube (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617230#action_12617230 ]
Brian M Dube commented on FOR-803:
----------------------------------
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select this_.ID as ID48_0_, this_.post_author as post2_48_0_, this_.post_date as post3_48_0_, this_.post_date_gmt as post4_48_0_, this_.post_content as post5_48_0_, this_.post_title as post6_48_0_, this_.post_category as post7_48_0_, this_.post_excerpt as post8_48_0_, this_.post_status as post9_48_0_, this_.comment_status as comment10_48_0_, this_.ping_status as ping11_48_0_, this_.post_password as post12_48_0_, this_.post_name as post13_48_0_, this_.to_ping as to14_48_0_, this_.pinged as pinged48_0_, this_.post_modified as post16_48_0_, this_.post_modified_gmt as post17_48_0_, this_.post_content_filtered as post18_48_0_, this_.post_parent as post19_48_0_, this_.guid as guid48_0_, this_.menu_order as menu21_48_0_, this_.post_type as post22_48_0_, this_.post_mime_type as post23_48_0_, this_.comment_count as comment24_48_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID54_0_, this_.post_author as post2_54_0_, this_.post_date as post3_54_0_, this_.post_date_gmt as post4_54_0_, this_.post_content as post5_54_0_, this_.post_title as post6_54_0_, this_.post_category as post7_54_0_, this_.post_excerpt as post8_54_0_, this_.post_status as post9_54_0_, this_.comment_status as comment10_54_0_, this_.ping_status as ping11_54_0_, this_.post_password as post12_54_0_, this_.post_name as post13_54_0_, this_.to_ping as to14_54_0_, this_.pinged as pinged54_0_, this_.post_modified as post16_54_0_, this_.post_modified_gmt as post17_54_0_, this_.post_content_filtered as post18_54_0_, this_.post_parent as post19_54_0_, this_.guid as guid54_0_, this_.menu_order as menu21_54_0_, this_.post_type as post22_54_0_, this_.post_mime_type as post23_54_0_, this_.comment_count as comment24_54_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID60_0_, this_.post_author as post2_60_0_, this_.post_date as post3_60_0_, this_.post_date_gmt as post4_60_0_, this_.post_content as post5_60_0_, this_.post_title as post6_60_0_, this_.post_category as post7_60_0_, this_.post_excerpt as post8_60_0_, this_.post_status as post9_60_0_, this_.comment_status as comment10_60_0_, this_.ping_status as ping11_60_0_, this_.post_password as post12_60_0_, this_.post_name as post13_60_0_, this_.to_ping as to14_60_0_, this_.pinged as pinged60_0_, this_.post_modified as post16_60_0_, this_.post_modified_gmt as post17_60_0_, this_.post_content_filtered as post18_60_0_, this_.post_parent as post19_60_0_, this_.guid as guid60_0_, this_.menu_order as menu21_60_0_, this_.post_type as post22_60_0_, this_.post_mime_type as post23_60_0_, this_.comment_count as comment24_60_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID66_0_, this_.post_author as post2_66_0_, this_.post_date as post3_66_0_, this_.post_date_gmt as post4_66_0_, this_.post_content as post5_66_0_, this_.post_title as post6_66_0_, this_.post_category as post7_66_0_, this_.post_excerpt as post8_66_0_, this_.post_status as post9_66_0_, this_.comment_status as comment10_66_0_, this_.ping_status as ping11_66_0_, this_.post_password as post12_66_0_, this_.post_name as post13_66_0_, this_.to_ping as to14_66_0_, this_.pinged as pinged66_0_, this_.post_modified as post16_66_0_, this_.post_modified_gmt as post17_66_0_, this_.post_content_filtered as post18_66_0_, this_.post_parent as post19_66_0_, this_.guid as guid66_0_, this_.menu_order as menu21_66_0_, this_.post_type as post22_66_0_, this_.post_mime_type as post23_66_0_, this_.comment_count as comment24_66_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID72_0_, this_.post_author as post2_72_0_, this_.post_date as post3_72_0_, this_.post_date_gmt as post4_72_0_, this_.post_content as post5_72_0_, this_.post_title as post6_72_0_, this_.post_category as post7_72_0_, this_.post_excerpt as post8_72_0_, this_.post_status as post9_72_0_, this_.comment_status as comment10_72_0_, this_.ping_status as ping11_72_0_, this_.post_password as post12_72_0_, this_.post_name as post13_72_0_, this_.to_ping as to14_72_0_, this_.pinged as pinged72_0_, this_.post_modified as post16_72_0_, this_.post_modified_gmt as post17_72_0_, this_.post_content_filtered as post18_72_0_, this_.post_parent as post19_72_0_, this_.guid as guid72_0_, this_.menu_order as menu21_72_0_, this_.post_type as post22_72_0_, this_.post_mime_type as post23_72_0_, this_.comment_count as comment24_72_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID78_0_, this_.post_author as post2_78_0_, this_.post_date as post3_78_0_, this_.post_date_gmt as post4_78_0_, this_.post_content as post5_78_0_, this_.post_title as post6_78_0_, this_.post_category as post7_78_0_, this_.post_excerpt as post8_78_0_, this_.post_status as post9_78_0_, this_.comment_status as comment10_78_0_, this_.ping_status as ping11_78_0_, this_.post_password as post12_78_0_, this_.post_name as post13_78_0_, this_.to_ping as to14_78_0_, this_.pinged as pinged78_0_, this_.post_modified as post16_78_0_, this_.post_modified_gmt as post17_78_0_, this_.post_content_filtered as post18_78_0_, this_.post_parent as post19_78_0_, this_.guid as guid78_0_, this_.menu_order as menu21_78_0_, this_.post_type as post22_78_0_, this_.post_mime_type as post23_78_0_, this_.comment_count as comment24_78_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID84_0_, this_.post_author as post2_84_0_, this_.post_date as post3_84_0_, this_.post_date_gmt as post4_84_0_, this_.post_content as post5_84_0_, this_.post_title as post6_84_0_, this_.post_category as post7_84_0_, this_.post_excerpt as post8_84_0_, this_.post_status as post9_84_0_, this_.comment_status as comment10_84_0_, this_.ping_status as ping11_84_0_, this_.post_password as post12_84_0_, this_.post_name as post13_84_0_, this_.to_ping as to14_84_0_, this_.pinged as pinged84_0_, this_.post_modified as post16_84_0_, this_.post_modified_gmt as post17_84_0_, this_.post_content_filtered as post18_84_0_, this_.post_parent as post19_84_0_, this_.guid as guid84_0_, this_.menu_order as menu21_84_0_, this_.post_type as post22_84_0_, this_.post_mime_type as post23_84_0_, this_.comment_count as comment24_84_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID90_0_, this_.post_author as post2_90_0_, this_.post_date as post3_90_0_, this_.post_date_gmt as post4_90_0_, this_.post_content as post5_90_0_, this_.post_title as post6_90_0_, this_.post_category as post7_90_0_, this_.post_excerpt as post8_90_0_, this_.post_status as post9_90_0_, this_.comment_status as comment10_90_0_, this_.ping_status as ping11_90_0_, this_.post_password as post12_90_0_, this_.post_name as post13_90_0_, this_.to_ping as to14_90_0_, this_.pinged as pinged90_0_, this_.post_modified as post16_90_0_, this_.post_modified_gmt as post17_90_0_, this_.post_content_filtered as post18_90_0_, this_.post_parent as post19_90_0_, this_.guid as guid90_0_, this_.menu_order as menu21_90_0_, this_.post_type as post22_90_0_, this_.post_mime_type as post23_90_0_, this_.comment_count as comment24_90_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID96_0_, this_.post_author as post2_96_0_, this_.post_date as post3_96_0_, this_.post_date_gmt as post4_96_0_, this_.post_content as post5_96_0_, this_.post_title as post6_96_0_, this_.post_category as post7_96_0_, this_.post_excerpt as post8_96_0_, this_.post_status as post9_96_0_, this_.comment_status as comment10_96_0_, this_.ping_status as ping11_96_0_, this_.post_password as post12_96_0_, this_.post_name as post13_96_0_, this_.to_ping as to14_96_0_, this_.pinged as pinged96_0_, this_.post_modified as post16_96_0_, this_.post_modified_gmt as post17_96_0_, this_.post_content_filtered as post18_96_0_, this_.post_parent as post19_96_0_, this_.guid as guid96_0_, this_.menu_order as menu21_96_0_, this_.post_type as post22_96_0_, this_.post_mime_type as post23_96_0_, this_.comment_count as comment24_96_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select this_.ID as ID102_0_, this_.post_author as post2_102_0_, this_.post_date as post3_102_0_, this_.post_date_gmt as post4_102_0_, this_.post_content as post5_102_0_, this_.post_title as post6_102_0_, this_.post_category as post7_102_0_, this_.post_excerpt as post8_102_0_, this_.post_status as post9_102_0_, this_.comment_status as comment10_102_0_, this_.ping_status as ping11_102_0_, this_.post_password as post12_102_0_, this_.post_name as post13_102_0_, this_.to_ping as to14_102_0_, this_.pinged as pinged102_0_, this_.post_modified as post16_102_0_, this_.post_modified_gmt as post17_102_0_, this_.post_content_filtered as post18_102_0_, this_.post_parent as post19_102_0_, this_.guid as guid102_0_, this_.menu_order as menu21_102_0_, this_.post_type as post22_102_0_, this_.post_mime_type as post23_102_0_, this_.comment_count as comment24_102_0_ from wp_posts this_ where this_.post_type=?
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
Hibernate: select t.* from wp_terms as t inner join wp_term_taxonomy as tt where t.term_id = tt.term_id and tt.taxonomy = 'category' and tt.count > 0
19:00:33.842 WARN!! GET /blog/category/uncategorized/index.html HTTP/1.1
java.lang.OutOfMemoryError: Java heap space
at java.util.jar.Manifest$FastInputStream.<init>(Manifest.java:300)
at java.util.jar.Manifest$FastInputStream.<init>(Manifest.java:295)
at java.util.jar.Manifest.read(Manifest.java:163)
at java.util.jar.Manifest.<init>(Manifest.java:52)
at java.util.jar.JarFile.getManifestFromReference(JarFile.java:163)
at java.util.jar.JarFile.getManifest(JarFile.java:145)
at sun.misc.URLClassPath$JarLoader$1.getManifest(URLClassPath.java:624)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:221)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at org.mortbay.util.Code.warning(Code.java:384)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:609)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1808)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1758)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:952)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:197)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:501)
> Profile new dispatcher plugins
> ------------------------------
>
> Key: FOR-803
> URL: https://issues.apache.org/jira/browse/FOR-803
> Project: Forrest
> Issue Type: Sub-task
> Components: Plugin: internal.dispatcher
> Reporter: Thorsten Scherler
>
> http://marc.theaimsgroup.com/?t=113830245600001
> El sáb, 28-01-2006 a las 23:10 +1100, David Crossley escribió:
> A while ago i noticed big performance problems.
> > e.g. building site-author took four times as long.
> >
> > We need to do at least basic profiling.
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113845026822103&w=2
> David was talking about v2 but this needs to be verified with the refactored version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.