As Racket CS slowly improves towards matching the mainline implementation, those results can give the impression that Racket CS is slow. To put things in context, look where Racket was already at in comparison to another very dynamic language, Python:

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

I don't know how to directly compare Python 3 and Racket CS on that site, but comparing three ways paints Racket CS in a more favorable light. Hopefully Racket CS will close the gap with Racket, but it’s already doing pretty great relatively... unless we compare to SBCL, Rust, Haskell, etc.

Note that several of these benchmarks use 4 cores on Python but only one on Racket. Time to revisit the Racket programs and use places.

Look at the single core benchmarks to get a more 1-1 comparison.