wg VS rustc-perf

These are issues that I'm aware of that are "tracking" the status of Rust on console:

* <https://github.com/rust-gamedev/wg/issues/90>

* <https://github.com/EmbarkStudios/rust-ecosystem/issues/18>

I say scare quote tracking because due to the nature of console NDAs it's unlikely you'll see much if any useful details in an open public forum.

The issues aren't dissimilar to those facing Godot (although it has the benefit it's able to use existing C++ compilers) and the project has previously outlined some of the issues involved:

* <https://docs.godotengine.org/en/4.0/tutorials/platform/conso...>

* <https://godotengine.org/article/godot-consoles-all-you-need-...>

The current "solution" seems to be console-related development activity occurring via the recently established W4 Games (https://w4games.com/2023/02/28/godot-support-for-consoles-is...) but that's obviously never going to be openly developed without console platform approval (same as any other game engine).

If as me (I am not using Rust to make commercial games yet, though), you accept that you won't be attempting to port itself to a console and let some third-party do it for you, you'll discover that there is already some discussion about it, people already managed to get it working on major consoles, but so far there are no publisher or other company officially doing port of Rust games.

A fast, Rust, JPEG 2000 decoder. Details here. The available options have either performance, cost, or licensing problems. I just need the decode part for classic JPEG 2000 at multi-resolution. Don't need tiles or video.

> Game developers should be investing their time in open tooling without contracts or restrictive licensing

Unfortunately, this is not possible in consoles, because of issues with NDA. Even Bevy can't have an open licensing there: https://github.com/rust-gamedev/wg/issues/90 (Godot also can't: https://docs.godotengine.org/en/stable/tutorials/platform/co...)

I expect that Bevy ports to consoles will take a cut of sales rather than a flat fee :(

rust-game-ports is now officially supported by the Rust GameDev WG. By having this repo on neutral ground, we want to invite the Rust gamedev community to contribute additional game examples to this bundle, so we may collectively expand our comparison-matrix of similar/same games made in different engines. A bit like the realworld app taken one step further.

There is a Github Discussion for this form: https://github.com/rust-gamedev/wg/discussions/121

https://github.com/rust-gamedev/wg/issues/90 ("Rust on Consoles")

> what do people use to run benchmarks on CI?

Typically, you purchase/rent a server that does nothing but sequentially run queued benchmarks (and the size/performance of this server doesn't really matter, as long as the performance is consistent), then sends the report somewhere for hosting and processing. Of course, this could be triggered by something running in CI, and the CI job could wait for the results, if benchmarking is an important part of your workflow.

But CI and benchmarks really shouldn't be run on the same host.

> What does the rust project use?

It's not clear exactly where the Rust benchmark "perf-runner" is hosted, but here are the specifications of the machine at least: https://github.com/rust-lang/rustc-perf/blob/414230abc695bd7...

> What do other projects use?

Essentially what I described above, a dedicated machine that runs benchmarks. The Rust project seems to do it via GitHub comments (as I understand https://github.com/rust-lang/rustc-perf/tree/master/collecto...), others have API servers that respond to HTTP requests done from CI/chat, others have remote GUIs that triggers the runs. I don't think there is a single solution that everyone/most are using.

A lot of effort is spent to reduce the size of structs in the Rust compiler

https://nnethercote.github.io/2023/03/24/how-to-speed-up-the...

3% and 6% of improvement doesn't seem like much, but at the level of rustc those big wins

Performance of Rustc must be continously tracked (here https://perf.rust-lang.org/) because if you don't proactively fight against bloat, the tendency is that the code will become slower over time (due to new features etc)

hmm really really hard to answer :'), it's tradeoffs I think, no matter what you think Rust (cmiiw, I'm not qualified to say this) has (and probably in the future will adds more with guards on compiler metrics https://perf.rust-lang.org/) several phases that given the diffs to other language, might not available to any language compiler out there, if it's available I think rustc already did their best in here (some already being parallized etc etc, might be wrong since I can't refs any reference MRs, but it does exists though labels regarding this)

About a year ago I was looking for a tool like Rust perf for my application code. I did some research and found a lot of prior art. However, nothing checked all the boxes I was looking for, so I built Bencher!

https://www.pingcap.com/blog/rust-compilation-model-calamity... is a good overview. In general it varies depending on the crate but we track the performance at https://perf.rust-lang.org/ - if you look at cargo, for example, over 60% of the time is spent in codegen through LLVM: https://perf.rust-lang.org/detailed-query.html?commit=222d1f...

Something like https://perf.rust-lang.org/?

The performance full-report link is dead: https://github.com/rust-lang/rustc-perf/blob/master/triage/2022-10-04.md