diff --git a/public/images/speedupWithPar.png b/public/images/speedupWithPar.png index f505996..6a4a3f5 100644 Binary files a/public/images/speedupWithPar.png and b/public/images/speedupWithPar.png differ diff --git a/src/pages/index.astro b/src/pages/index.astro index 4748cd7..a19d2db 100644 --- a/src/pages/index.astro +++ b/src/pages/index.astro @@ -756,11 +756,13 @@ const vscodeSlides = [

In Flix, every compiler phase is parallel. The plot on the right shows - the speed-up of each compiler phase when run on a 24 core machine. + the speed-up of each compiler phase when run with 24 threads on an AMD + Ryzen 9 5900X with a 12‑core CPU.

In other words, Flix can take full advantage of modern hardware, - leading to speed-ups of between 5x – 7x on multi-core machines. + leading to speed-ups of up to 7.9x per phase and 4.9x for + the compiler as a whole.

Furthermore, the Flix compiler is incremental which leads to @@ -785,30 +787,30 @@ const vscodeSlides = [

Compiler Performance: The Raw Numbers

The following table illustrates the performance of the Flix compiler - on an Apple M2 Pro with a 10‑core CPU running on OpenJDK 26: + on an AMD Ryzen 9 5900X with a 12‑core CPU running on OpenJDK 27:

- + 303,740 lines/sec - + 100,645 lines/sec
Throughput (entire compiler):Throughput (frontend only): 64,956 lines/sec
Throughput (frontend only):Throughput (entire compiler): 133,287 lines/sec

- The above results can be reproduced by running the commands: java -jar flix.jar Xperf --n 21 and java -jar flix.jar Xperf --frontend --n 21. + Reproduce with java -Xms8g -Xmx8g -jar flix.jar Xperf --par --n 500.

The Flix compiler achieves these results despite supporting costly