Question: Say we have the following classes:

```
class DoubleOhSeven {
  public static void doSomethingClassy();
  public static void neverDoThisClassy();
}

class Dude {
  public void doSomething();
  public void neverDoThis();
}

public class Party {
  public static void main(String[] args){
    DoubleOhSeven.doSomething();
    Dude guy = new Dude;
    guy.doSomething();
  }
}

```

Of course, all the methods will be compiled into their respective `.class`: do the unused static/instance methods occupy memory at run time? What about unused inherited or imported methods?

Answer: 
The unused methods are still there occupying memory as part of the class / object, even if they're not directly called.

If they were optimised away, then that would make reflective calls on these methods impossible.

One could argue that an optimisation could be generated that only stored the method stub in memory, and garbage collected the method contents (which would then be re-fetched from the class file if a call was made.) However, I'm not aware of a VM which does this, and it would be hard to justify due to the likely minimal gains in memory and tradeoff in speed whenever such a method was called.

Unused inherited methods would be exactly the same.
The memory used by an instance of a class `Abc` does not depend on how many methods there are in `Abc`.

The generated bytecode obviously does increase in size when you add methods, whether they do something or not, but that would only affect the size of the class object `Abc.class`, which is loaded only once, regardless of how many instances are created.