Skip to content

Possible performance regression in WASM builds #11122

@eerii

Description

@eerii

Bevy version

  • Original: 0.12.1
  • Current: 8067e46

Relevant system information

Please include:

Cargo version: cargo 1.76.0-nightly

OS: Arch Linux, Kernel 6.6.7

CPU: Intel(R) Core(TM) i7-4770HQ

GPU: None (integrated)

Using trunk for builds.

What's performing poorly?

Updating from 0.12.1 to main makes wasm builds very slow, they take 100% of the GPU and drop a lot of frames. This doesn't happen with native builds, they run the same as before. I tested it on an empty 2d scene with a camera.

Before and After Traces

Additional information

Minimum example (2d shapes from the examples folder with minimum trunk setup)
minimum_project.zip

100ms before

100ms before

100ms after

100ms after

100ms native (no lag) tracy

image

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-BugAn unexpected or incorrect behaviorC-PerformanceA change motivated by improving speed, memory usage or compile timesO-WebSpecific to web (WASM) buildsP-RegressionFunctionality that used to work but no longer does. Add a test for this!

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions