On 07/16/2014 05:44 PM, Lars Buitinck wrote:
> 2014-07-16 17:29 GMT+02:00 Andy :
>> That is using google perftools.
> I thought you were referring to the bit about gprof.
Oh, I think I misread that bit.
>
>> So you get line-by-line with google perftools without using debugging
>> versions? How?
> I
now way to really get line by line without some sort of debug afaik, it
throws the info away at compile time
On Wed, Jul 16, 2014 at 11:44 AM, Lars Buitinck wrote:
> 2014-07-16 17:29 GMT+02:00 Andy :
> > That is using google perftools.
>
> I thought you were referring to the bit about gprof.
>
2014-07-16 17:29 GMT+02:00 Andy :
> That is using google perftools.
I thought you were referring to the bit about gprof.
> So you get line-by-line with google perftools without using debugging
> versions? How?
I don't, I look at per-function cost.
---
On 07/16/2014 05:17 PM, Lars Buitinck wrote:
> 2014-07-16 16:43 GMT+02:00 Andy :
>> I'm pretty sure I could use yep for profiling, as mentioned in the docs:
>> http://scikit-learn.org/dev/developers/performance.html#profiling-compiled-extensions
>> and get line-by-line counts.
>> However I did not
2014-07-16 16:43 GMT+02:00 Andy :
> I'm pretty sure I could use yep for profiling, as mentioned in the docs:
> http://scikit-learn.org/dev/developers/performance.html#profiling-compiled-extensions
> and get line-by-line counts.
> However I did not manage to do that recently. I ususally got the cyth
Hey all.
A slightly off-topic question about cython profiling.
I'm pretty sure I could use yep for profiling, as mentioned in the docs:
http://scikit-learn.org/dev/developers/performance.html#profiling-compiled-extensions
and get line-by-line counts.
However I did not manage to do that recently. I
