in reply to Making sense of some dprof output

Here is some dprofpp -I output, for almost the same program on different input sizes

"almost the same" means different. "different input sizes" also different. That's at least four possible combinations.

And you've posted what appear to be three different sets of timings. And a reference to one piece of code.

You then ask:

The question is why is the elapsed time always double for this program?

"double" what? Which "this program" are you refering to? And to what are you comparing it?

As the saying goes: insufficient data.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Replies are listed 'Best First'.
Re^2: Making sense of some dprof output
by PoorLuzer (Beadle) on May 19, 2009 at 03:36 UTC
    Extremely valid points . the programs are just simple variants of each other and I felt posting the same code would not make much sense. Anyways, I will ditch dproff and use NYT, and then come back with more data!