Numbers, But With Context

These benchmark views use realistic mock data to show how the two languages usually behave under different workload profiles. The point is not to pretend every program gets the same ratio. The point is to show the shape of the trade-offs.

profile.cfg

CURRENT PROFILE

Steady load

Lower is better. Native code usually keeps a lead when the workload is continuous and allocation patterns stay controlled.

method_notes.txt

Equivalent algorithms, not deliberately bad Java.
Modern x86-64 workstation assumptions.
Numbers illustrate likely order-of-magnitude deltas.
Tail-latency and startup are often more important than average throughput.

chart.dat

latency.log

raw_table.csv

WORKLOAD	C++	JAVA

notes.md

Execution

C++ benefits from native code generation, direct memory models, and fewer managed-runtime constraints.

Memory

Java often spends more memory on object headers, heap behavior, and runtime baseline overhead.

Startup

Native binaries win visibly when tools are short-lived or when processes are created frequently.