ProAdvancedInterview prep

Java Performance

What actually costs on the JVM, read off code rather than a stopwatch: the allocation that never happens, the concat loop that copies everything twice, the map that rehashes sixteen times on its way to a million entries. Ten spines on the difference between the operation you wrote and the work the VM does.

Questions90
Topics10
Answering time68 minutes
At five a day18 days
LevelAdvanced

Who it is for

Has never measured anything.

For someone confident in the language who wants the traps, the edge cases and the interview questions.

You will get the most out of it if you have written Java recently enough to read it without effort, and have been surprised by it at least once. If you are picking the language up for the first time, start with Java Essentials and come back to this one.

It is also built for interview preparation: the questions are the ones that get asked because they separate people who have read the documentation from people who have hit the behaviour in production.

How long it takes

90 graded questions at roughly 45 seconds each is about 68 minutes of answering in total.

At the default five questions a day, and because the session mixes in your other courses, expect around 18 days — call it 3 weeks — to see everything once, plus a few weeks of thinning reviews after that before it is all mastered.

A question is mastered on the third correct answer, once the gap between reviews has grown past a week — so a course cannot be finished in a weekend however long you sit with it.

Question mix

  • 60 multiple choice
  • 10 concept cards
  • 10 predict the output
  • 10 put it in order
  • 10 matching questions

Syllabus

What you will be asked about

  1. 01

    What Allocation Costs

    Explain what a `new` really costs on HotSpot and when escape analysis removes it.

  2. 02

    Concatenation and Builders

    Predict the allocation cost of string building and pick the construct that avoids it.

  3. 03

    ArrayList Growth and Capacity

    Separate size from capacity and predict which list operations copy or shift.

  4. 04

    Boxes and Primitives

    Predict when a number gets boxed and what that box costs in memory and identity.

  5. 05

    HashMap Resizing and Hashing

    Size a map so it never rehashes, and spot the key that makes hashing useless.

  6. 06

    Exceptions as Control Flow

    Locate the real cost of an exception and decide when a throw is too expensive.

  7. 07

    JIT Warmup and Measurement

    Explain why an untimed first run is meaningless and what a real benchmark controls for.

  8. 08

    Interning and the Constant Pool

    Decide when two equal Strings are the same object and what interning really buys.

  9. 09

    Streams Against Loops

    Predict when a pipeline does less work than a loop and when its overhead dominates.

  10. 10

    Generations and Stop-the-World

    Say what a collection actually costs and what a pause does and does not stop.

8 more topics, and all 90 questions

Java Performance is a Pro course. One subscription opens it and every other course in the catalogue, including the ones still being written.

See pricing Find a free course

A question from this course

What Allocation Costs

What does this print?

public class Main {
  static class P { int x; P(int x){this.x=x;} }
  public static void main(String[] args) {
    P p = null;
    for (int i = 0; i < 3; i++) p = new P(i);
    System.out.println(p.x);
  }
}
  • Anull
  • B2
  • C0
  • D3
Show the answer

B 2

The loop allocates three P objects and keeps only the last, so p.x is 2. You may have expected 0 if you read the assignment as filling a variable that is already taken, or 3 by reading the loop counter after it exits. The point for performance is that two of the three objects became garbage before the loop ended, and objects that die in Eden are the cheapest kind the collector ever handles.

The rest of the track

Java at every depth

FreeFoundation

Java Essentials

The behaviour underneath the ceremony: what a variable really holds, why 1/2 is 0, and why two Strings that look identical are not always the same object. Ten spines on the code that compiles cleanly and still does something else.

90 questions · 68 minutes

ProCore

Java Core

Where Java trips developers who use it every day: autoboxing that hides a NullPointerException, a ternary that quietly unboxes, and dispatch rules that pick a method before the program runs. Ten spines on the gap between what the code says and what the JVM does.

90 questions · 68 minutes

ProCore

Java Data & Collections

The collections framework taken seriously: which container promises what, why remove(1) deletes a position, and how a mutated key disappears from its own HashMap. Ten spines on the containers you use every day and the contracts underneath them.

90 questions · 68 minutes

ProCoreInterview prep

Java Errors & Edge Cases

Exceptions at the points where they stop behaving the way you assumed: a finally block that discards the exception unwinding through it, a map lookup that throws on the way into an int, a class that fails once and reports a missing definition forever after. Ten spines on the paths your happy-path code never takes.

90 questions · 68 minutes

ProCore

Java Standard Library

The library people reimplement by hand: what split really returns, StringBuilder, Optional, streams and collectors, comparators, java.time, the Objects helpers and text blocks. Ten built-ins that already do the job, and one behaviour in each that is not the one you assumed.

90 questions · 68 minutes

ProAdvanced

Java Idioms & Pitfalls

The Java people write out of habit that is wrong or dated: raw types, boxed equality, catching Exception, building strings in a loop, arrays where a List belongs and getters that hand out the field. Ten habits, each one run to see what it actually does.

90 questions · 68 minutes

ProAdvancedInterview prep

Java Advanced

The traps a confident Java reader still walks into: erasure, wildcard variance, dispatch decided before the program runs, and a constructor that sees a field before it is assigned. Ten spines of code that compiles cleanly and behaves otherwise.

90 questions · 68 minutes

ProCore

Java Testing

What a Java test actually asserts, and where that claim is weaker than it looks. Argument order and failure messages, the three kinds of equality, deltas, throwing, fixtures and static state, test doubles, and the difference between a failure and an error.

90 questions · 68 minutes

ProAdvancedInterview prep

Java Interview Questions

The Java an interviewer actually probes, answered from the rules rather than from memory. The equals and hashCode contract, the string pool, references and boxing, collections, erasure, checked exceptions, dispatch, immutability, and the what-does-this-print questions behind them.

90 questions · 68 minutes

Start Java Performance
in tomorrow’s session.

Enrol and this course joins your daily five, mixed in with everything else you are studying — 90 questions spread over about 18 days rather than dropped on you at once.

Browse the catalogue