News for hackers. Stuff that matters.
Re:Practices for writing high-performance Go by galangalalgol on Tuesday May 07, 2019 @06:49AM (#19848199)
The benchmark game puts c, rust, and c++, in that order, roughly on par in performance, with go being about 2-3x slower. No idea if that's accurate. Sampling bias means people who like performance are optimizing the languages used for performance, and people who just like to get something working quit after the first benchmark in go or python is finished. https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
Re:Practices for writing high-performance Go by v_lisivka on Tuesday May 07, 2019 @10:01AM (#19849384)
If you discard regexredux, then Rust is faster than C and C++ at average: see average bar at "How many times slower graph" [1].

regexredux program is outlier in Rust, because replacement of a regex in string is slower in regex crate, because author of regex crate chose to implement safer, but slower algorithm. To fix this, regex crate must be updated or replaced. I spent two weekends on this.

[1]: https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

Re:Practices for writing high-performance Go by igouy on Wednesday May 08, 2019 @02:01AM (#19856242)
> To fix this, regex crate must be updated or replaced.

I somehow doubt pcre2 is being changed to make the tiny toy C programs run better.

> I spent two weekends on this.

So shouldn't we assume the program performance simply reflects all-those-hours you've spent working on it?

Re:Practices for writing high-performance Go by v_lisivka on Wednesday May 08, 2019 @05:21AM (#19857179)
Look at the program:

  fn find_replaced_sequence_length(sequence: String) -> usize {
    // Replace the following patterns, one at a time:
    let substs = vec![
        ("tHa[Nt]", "<4>"),
        ("aND|caN|Ha[DS]|WaS", "<3>"),
        ("a[NSt]|BY", "<2>"),
        ("<[^>]*>", "|"),
        ("\\|[^|][^|]*\\|", "-"),
    ];
  
    // Perform the replacements in the sequence:
    substs
        .iter()
        .fold(sequence, |s, (re, replacement)| {
            regex(re)
                .replace_all(&s, NoExpand(replacement)).into_owned()
        }).len()
  }

It measures performance of RE engine. I can switch from regex crate to PCRE2, and program performance will match C.
Re:Practices for writing high-performance Go by igouy on Wednesday May 08, 2019 @11:12AM (#19859555)
> I can switch from regex crate to PCRE2, and program performance will match C.

Perhaps it would; those measurements have not been made.

What does that have to do with re-writing libraries to make tiny toy programs run better?

What does that have to do with program performance being a proxy for programmer effort?

Re:Practices for writing high-performance Go by igouy on Tuesday May 07, 2019 @12:07PM (#19850777)
mandelbrot is outlier in Rust, because… :-)
Re:Practices for writing high-performance Go by v_lisivka on Tuesday May 07, 2019 @04:10PM (#19852997)
Because hardware acceleration is used in C and C++ versions. I will fix this soon.
Re:Practices for writing high-performance Go by igouy on Friday May 10, 2019 @01:59PM (#19880449)
> Sampling bias means people who like performance are optimizing the languages used for performance …

Also, there might be a something to prove "bias" :-)