Open krono opened 10 years ago
Should we focus on the current shootout benchmark set? In the above benchmarks a lot of older, currently phased out benchmarks are listed. the current set is:
binary-trees chameneos-redux fannkuch-redux fasta k-nucleotide mandelbrot meteor-contest n-body pidigits regex-dna reverse-complement spectral-norm thread-ring
An unfortunately high percentage of these involve regular expressions. If they just need something simple that's not performance critical, we could maybe support that, but not the others.
The set I'd most like to focus on is those in my pldi 11 paper, which Racket has previously been compared on.
The set from this paper is (shootout part):
Mandelbrot* seem to not really work for me, I get primitive regexp-match? is not yet implemented
I think @krono changed that to error instead of always returning true.
Yes, thanks for the catch. I’ll try to patch the benches where regexes are not actually necessare
I think the benchmark "uses" regexps by requiring a library that loads them. We just need to put that hack back in.
well, loading does not trigger the not-implemented-error, calling does.
Probably someone in racket/port
does this, so, yes for regex-match?
the hack may be justified
@krono can you update the status here?
will do
status is up-to-date
These are the shootout benches
chameneossamth/pycket#116 (threads)cheapconcurrencysamth/pycket#116 (threads)echoneeds threads (threads)samth/pycket#112samth/pycket#90samth/pycket#90samth/pycket#120samth/pycket#90samth/pycket#115samth/pycket#117samth/pycket#121 (regex)samth/pycket#90samth/pycket#119thread-ringno outputsamth/pycket#118