You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Paul Joseph Davis (JIRA)" <ji...@apache.org> on 2010/10/09 02:25:31 UTC

[jira] Resolved: (COUCHDB-93) Add option to run CouchDB with Erlang's profiling tools

     [ https://issues.apache.org/jira/browse/COUCHDB-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Joseph Davis resolved COUCHDB-93.
--------------------------------------

    Resolution: Fixed

Builds with coverage enabled are now supported. Profiling is an involved excercise that's best done from an interactive couchdb prompt or using custom code.

> Add option to run CouchDB with Erlang's profiling tools
> -------------------------------------------------------
>
>                 Key: COUCHDB-93
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-93
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Build System
>            Reporter: Jan Lehnardt
>            Assignee: Jan Lehnardt
>            Priority: Minor
>             Fix For: 1.0.2
>
>
> Erlang comes with a set of code coverage and profiling tools that can be helpful to track down performance problems as well as performance regressions over time. It would be nice if it would be easy to profile CouchDB with these tools. 
> coverage needs a different build, so --with-coverage makes sense.
> Profiling does not need a recompilation and would best
> served (IMHO) as couchdb --profile-function-calls and --profile-function-times
> or however that would be integrated into the command.
> couchdb --profile=function-calls --profile=function-call-times
> --profile=function-fall-times-cpu or have some way to pass
> options down to the profiler, you get the idea, some way of
> specifying at runtime how to profile CouchDB.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.