forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Blaschke (JIRA)" <>
Subject [jira] Updated: (FOR-572) run a memory profiler while forrest is operating
Date Mon, 29 Aug 2005 18:58:05 GMT
     [ ]

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

The profiling results can be accessed via http://localhost:8888/profile.html during "forrest
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
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


> run a memory profiler while forrest is operating
> ------------------------------------------------
>          Key: FOR-572
>          URL:
>      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:
For more information on JIRA, see:

View raw message