title: How to measure efficiency (in particular: assembly code) for java programs?
body: <p>I have asked questions whose answers often faced me in the direction of efficiency. Rather than continuing asking these type of questions I would rather look beforehand at the efficiency. However there are of course many different types of efficiency. The number of lines in code, assembly, the time it takes to write, the time it takes for a computer to execute. And I probably miss a lot more ways to look at it.</p>
  
  <p>Because there are so many ways to look at efficiency, I would like to start with <strong>how do you get the assembly code of your own code and stop at the right spot within your code?</strong> (Let's say you have 500 lines of code and you're interested in line 450 to 460). I am not sure if this is already a feature found in IDEs, if so how could I find functions like these? (= What is the naming of these sort of things so that I can find it for my own IDEs if it has this feature).</p>
  
  <p>(There is already a lot of information about efficiency at Stack Overflow, I looked at many of them, however I found it hard to get a feel of what people often start with when they analyse their code. Do they start with studying their code, then assembly or do they just use an IDE to find the most expensive methods and change them this way? This is a bad question because it of course depends on a lot on different factors, but I hope to get at least a little bit more feel for it and I think an answer to this question might help.) </p>