forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Williams (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FOR-572) run a memory profiler while forrest is operating
Date Sat, 15 May 2010 11:59:41 GMT

     [ 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.


Mime
View raw message