3 ms·
Not necessarily longest, though. Right? Most executed would also suffice. Beware measuring, though. Sometimes, just thinking about the problem ahead of time
by taeric 8y ago
Not necessarily longest, though. Right? Most executed would also suffice.
Beware measuring, though. Sometimes, just thinking about the problem ahead of time can clearly expose where you are spending time. At least, it can give a hypothesis to test for where you are spending time. With measurements to confirm/refute. :)
- paulddraper 8y ago> Not necessarily longest, though. Right? Most executed would also suffice "Longest total." I don't care if its a big slice of pie or a lot of little slices. But it better be one of those. > Sometimes, just thinking about the problem ahead of time can clearly expose where you are spending time. That's certainly true. But 99% of people overestimate their ability to do this. And are surprised by the results.
- CarolineW 8y agoSo when you say "longest" you don't mean "longest section of code", I'm guessing you mean "section of code in which execution spends the longest time". If so, good, but it wasn't clear to me that that's what you meant. If you mean something else then I don't know what you mean at all.
- paulddraper 8y ago"Longest" seemed clear to me. (Over "largest" and "slowest".)
- CarolineW 8y agoBut you wrote it, so of course it's clear to you. To me, when someone says "the longest part of the program" I immediately think of the routine that stretches over the most lines. That's the longest part of the code.
- PeterisP 8y agoIDK, "longest part of code" to me clearly seems to refer to length of the code (i.e. lines of code), not to length of its execution time; so I'd say that there definitely seems to be some confusion caused by the choice of words.
- taeric 8y agoJust to further these two posts, that is why I asked my question at the top here. "Hottest" code, I thought, was already well established for most executed. I had never seen "longest" for anything. To that end, I was taking it to mean that longest "synchronous" path through your system. Not necessarily a single method, by any measure. But, systems have plenty of what I will call "checkpoints" where code can be restarted/rerun with no hard to recover penalty. That is what I took to mean by longest.
- scott_s 8y ago> Beware measuring, though. Sometimes, just thinking about the problem ahead of time can clearly expose where you are spending time. Why beware measuring? In my experience, people are generally terrible at guessing where the bulk of the time is being spent. Measure as soon as you care.
- taeric 8y agoApologies, I meant that as blind measuring. Don't just get a reading and take action. Hypothesize about where you think the time is spent and measure to test your hypothesis. And always question why the time is spent where it is.