Always-on AV1 in --release; opt-in to nasm-optimizations

[emilk]

What

Even without nasm, it is pretty fast.

I also added a warning to the user that they can get more performance by enabling the nasm feature.

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested the web demo (if applicable):
  • Using examples from latest main build: rerun.io/viewer
  • Using full set of examples from nightly build: rerun.io/viewer
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
• If applicable, add a new check to the release checklist!
• If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

• PR Build Summary
• Recent benchmark results
• Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

[github-actions]

Deployed docs

Commit	Link
3533997	https://landing-nadqul8es-rerun.vercel.app/docs

[nikolausWest]

Can a python & pip user get the nasm optimization without compiling form source? If not, it probably shouldn't be a prominent warning

[emilk]

The nasm feature is on by default for our pip package build, so they won't see a warning.

The warning is for users that do cargo install rerun-cli

[Wumpf]

title a bit misleading. It's still off on debug

[Wumpf]

how are we building the standalone executables that we upload to GH? Those should also get that feature flag

[emilk]

how are we building the standalone executables that we upload to GH? Those should also get that feature flag

Good question. I'v created a separate issue for it:

• Make sure we compile the binaries we upload to GitHub with -F nasm #7669