Issue #21566 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Assigned Assignee set to hsbt (Hiroshi SHIBATA) ---------------------------------------- Misc #21566: Transfer Shopify/yjit-bench and speed.yjit.org to ruby/ruby-bench and *.ruby-lang.org https://bugs.ruby-lang.org/issues/21566#change-114532 * Author: k0kubun (Takashi Kokubun) * Status: Assigned * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- ## Proposal 1. Transfer `Shopify/yjit-bench` to `ruby/ruby-bench` on GitHub * Let `@ruby/jit` (YJIT/ZJIT developers) maintain the repository 2. Host `speed.yjit.org` on `*.ruby-lang.org` * @ufuk proposed `speed.ruby-lang.org`. Another idea: `bench.ruby-lang.org` ## Background [yjit-bench](https://github.com/Shopify/yjit-bench) has collected useful application-level benchmarks for Ruby, which have been used for other Ruby implementations as well. It can be used without YJIT and is useful as a general Ruby benchmark suite, so it might make more sense to call it "ruby-bench" under the Ruby organization. [speed.yjit.org](https://speed.yjit.org/) is a website that visualizes the benchmark results of `yjit-bench` every day. It's useful for monitoring the CRuby performance in general, so we could have it as a `ruby-lang.org` website, not a YJIT one. --- @ufuk has originally proposed the idea of (2) to @hsbt and he's onboard with it. I'm filing this here for public awareness and discussions. -- https://bugs.ruby-lang.org/

Issue #21566 has been updated by Eregon (Benoit Daloze). How about renaming to ruby/ruby-bench as proposed in the issue description? Will that be done as a second step maybe? I think it would make a lot of sense to call it ruby/ruby-bench, that benchmark suite is effectively not specific to YJIT and it's the most comprehensive realistic benchmark suite we have for realistic Ruby workloads (as @k0kubun said). ---------------------------------------- Misc #21566: Transfer Shopify/yjit-bench and speed.yjit.org to ruby/ruby-bench and *.ruby-lang.org https://bugs.ruby-lang.org/issues/21566#change-114548 * Author: k0kubun (Takashi Kokubun) * Status: Assigned * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- ## Proposal 1. Transfer `Shopify/yjit-bench` to `ruby/ruby-bench` on GitHub * Let `@ruby/jit` (YJIT/ZJIT developers) maintain the repository 2. Host `speed.yjit.org` on `*.ruby-lang.org` * @ufuk proposed `speed.ruby-lang.org`. Another idea: `bench.ruby-lang.org` ## Background [yjit-bench](https://github.com/Shopify/yjit-bench) has collected useful application-level benchmarks for Ruby, which have been used for other Ruby implementations as well. It can be used without YJIT and is useful as a general Ruby benchmark suite, so it might make more sense to call it "ruby-bench" under the Ruby organization. [speed.yjit.org](https://speed.yjit.org/) is a website that visualizes the benchmark results of `yjit-bench` every day. It's useful for monitoring the CRuby performance in general, so we could have it as a `ruby-lang.org` website, not a YJIT one. --- @ufuk has originally proposed the idea of (2) to @hsbt and he's onboard with it. I'm filing this here for public awareness and discussions. -- https://bugs.ruby-lang.org/

Issue #21566 has been updated by k0kubun (Takashi Kokubun). Status changed from Assigned to Closed We've published https://speed.ruby-lang.org/. Thank you @hsbt! ---------------------------------------- Misc #21566: Transfer Shopify/yjit-bench and speed.yjit.org to ruby/ruby-bench and *.ruby-lang.org https://bugs.ruby-lang.org/issues/21566#change-114645 * Author: k0kubun (Takashi Kokubun) * Status: Closed * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- ## Proposal 1. Transfer `Shopify/yjit-bench` to `ruby/ruby-bench` on GitHub * Let `@ruby/jit` (YJIT/ZJIT developers) maintain the repository 2. Host `speed.yjit.org` on `*.ruby-lang.org` * @ufuk proposed `speed.ruby-lang.org`. Another idea: `bench.ruby-lang.org` ## Background [yjit-bench](https://github.com/Shopify/yjit-bench) has collected useful application-level benchmarks for Ruby, which have been used for other Ruby implementations as well. It can be used without YJIT and is useful as a general Ruby benchmark suite, so it might make more sense to call it "ruby-bench" under the Ruby organization. [speed.yjit.org](https://speed.yjit.org/) is a website that visualizes the benchmark results of `yjit-bench` every day. It's useful for monitoring the CRuby performance in general, so we could have it as a `ruby-lang.org` website, not a YJIT one. --- @ufuk has originally proposed the idea of (2) to @hsbt and he's onboard with it. I'm filing this here for public awareness and discussions. -- https://bugs.ruby-lang.org/