pnoise

There's some benches between various languages, including Crystal as well, for those interested https://github.com/kostya/benchmarks EDIT: There's also this: https://github.com/nsf/pnoise

My experience with compiler development is that the incentives all align toward making the "default RNG that people go to" as fast as possible to the exclusion of all else, including the quality of the generated numbers. That's because people frequently write benchmarks gated on the speed of random number generation, and those benchmarks usually don't care about the quality of the random numbers. Sometimes those benchmarks get popular, which encourages a race to the bottom in RNG quality. (Similar incentives exist for hash functions, by the way.) Popular RNG-bound benchmarks: * "fasta" from the Benchmarks Game [1] (thankfully, this one mandates use of its own RNG, though it's vulnerable to fast-forwarding as demonstrated in [2]) * "Perlin noise" [3] (almost entirely RNG performance bound) * From SunSpider (this one being particularly rele

> Bounds checking is optional in Rust too. Could've sworn I've read somewhere the Rust maintainers stated that Rust will never have a switch to disable bounds checking. Has this changed? > Can you elaborate as to other ways Rust has worse performance? I don't know of any other specifics, but benchmarks usually show D outperform Rust (and often enough, everything else), e.g.: https://togototo.wordpress.com/2013/07/23/benchmarking-level... https://github.com/nsf/pnoise

Yes. There are some here: https://github.com/kostya/benchmarks Here's another one: https://github.com/nsf/pnoise And then in the samples directory ( https://github.com/manastech/crystal/tree/master/samples ) there are some more but without time results (but you can try them yourself).