You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "David Crossley (JIRA)" <ji...@apache.org> on 2005/07/11 03:27:12 UTC
[jira] Created: (FOR-572) run a memory profiler while forrest is operating
run a memory profiler while forrest is operating
------------------------------------------------
Key: FOR-572
URL: http://issues.apache.org/jira/browse/FOR-572
Project: Forrest
Type: Task
Components: Core operations
Versions: 0.8-dev
Reporter: David Crossley
Fix For: 0.8-dev
We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is operating
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12319537 ]
David Crossley commented on FOR-572:
------------------------------------
Another relevant thread:
Profiling Forrest [FOR-572]
http://marc.theaimsgroup.com/?l=forrest-dev&m=112456323907116
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.8-dev
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is operating
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12322595 ]
Ross Gardler commented on FOR-572:
----------------------------------
No idea if this is any use, just spotted a reference to it on Cocoon user list:
http://svn.apache.org/viewcvs.cgi/cocoon/branches/BRANCH_2_1_X/tools/instrumentation/readme.txt?view=markup
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.8-dev
> Attachments: step1_profiling.patch
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is operating
Posted by "Ron Blaschke (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=all ]
Ron Blaschke updated FOR-572:
-----------------------------
Attachment: step1_profiling.patch
This patch adds partial support for profiling through Cocoon pipelines.
You still need to replace the /standard pipes/ with the /profiling pipes/ in
sitemap.xmap.
The profiling results can be accessed via http://localhost:8888/profile.html during "forrest run".
Note that you need to load a page first, to get some profiling data.
Also note that after this change "profile.html" is reserved for the profiling page. This will
go away after step 1 below, I guess.
Next steps probably are:
1) Refactor profiler.xmap into a (output) plugin, probably including a profile2document stylesheet
2) Find out how to automatically replace the pipes with their profiling counterparts
3) Find out how to best get some "profile.html" during static site generation
Ron
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.8-dev
> Attachments: step1_profiling.patch
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is operating
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12315449 ]
David Crossley commented on FOR-572:
------------------------------------
A couple of recent forrest-dev threads:
[HEADS_UP] SVN HEAD is broken
http://marc.theaimsgroup.com/?l=forrest-dev&m=112086829603887
possible memory problems
http://marc.theaimsgroup.com/?l=forrest-dev&m=111958832520115
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Fix For: 0.8-dev
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is operating
Posted by "Ron Blaschke (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12318705 ]
Ron Blaschke commented on FOR-572:
----------------------------------
I reported the issue to Cocoon.
Possible Memory Leak with LinkRewriterTransformer
http://issues.apache.org/bugzilla/show_bug.cgi?id=36162
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.8-dev
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is operating
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=all ]
Ross Gardler updated FOR-572:
-----------------------------
Fix Version: (was: 0.8-dev)
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Attachments: step1_profiling.patch
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is operating
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=all ]
David Crossley updated FOR-572:
-------------------------------
Priority: Critical (was: Major)
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.8-dev
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is operating
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12318565 ]
David Crossley commented on FOR-572:
------------------------------------
Another separate discussion thread:
Quick glimpse at Forrest's build times
http://marc.theaimsgroup.com/?t=112377044900006
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.8-dev
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is
operating
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=all ]
Ross Gardler updated FOR-572:
-----------------------------
Fix Version: 0.8-dev
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.8-dev
> Attachments: step1_profiling.patch
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is
operating
Posted by "Tim Williams (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=all ]
Tim Williams updated FOR-572:
-----------------------------
Fix Version: 0.9
(was: 0.8-dev)
As David suggested in the mail below, this is an issue that is a holding area for lots of good info. This should just be turned into a doc somewhere.
http://marc.theaimsgroup.com/?t=115188972100002&r=1&w=2
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.9
> Attachments: step1_profiling.patch
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is operating
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12331349 ]
David Crossley commented on FOR-572:
------------------------------------
Related to comment above [29/Aug/05 08:57 PM] ...
See a description of how to run the basic Cocoon Profiler
http://forrest.apache.org/docs_0_80/howto/howto-dev.html#debug
... profiling is much more of course, but that is a start.
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.8-dev
> Attachments: step1_profiling.patch
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is
operating
Posted by "Tim Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Williams updated FOR-572:
-----------------------------
Fix Version/s: 0.10
(was: 0.9-dev)
Honestly, I don't know what the real issue is here. The other one, FOR-591, had a concrete, testable problem but this one doesn't. It does have tons of good references though. I'm moving to 0.10 for now. If someone can articulate what the problem is, we can move it back.
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: https://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Issue Type: Task
> Components: Core operations
> Affects Versions: 0.8
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.10
>
> Attachments: step1_profiling.patch
>
>
> We need to run a memory profiler while forrest is operating.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-572) run a memory profiler while forrest is operating
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12318434 ]
David Crossley commented on FOR-572:
------------------------------------
Another separate discussion thread:
Deeper Look at Memory Issue, Maybe Successful
http://marc.theaimsgroup.com/?t=112371108100008
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.8-dev
>
> We need to run a memory profiler while forrest is operating.
--
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-572) run a memory profiler while forrest is operating
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12320521 ]
David Crossley commented on FOR-572:
------------------------------------
Thanks. Applied patch step1_profiling.patch (3 kb)
> run a memory profiler while forrest is operating
> ------------------------------------------------
>
> Key: FOR-572
> URL: http://issues.apache.org/jira/browse/FOR-572
> Project: Forrest
> Type: Task
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Priority: Critical
> Fix For: 0.8-dev
> Attachments: step1_profiling.patch
>
> We need to run a memory profiler while forrest is operating.
--
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