It is not expected to use all cores. We deliberately designed it this way because the target audience tends to have a low core count and this kept the complexity down. It also keeps the performance on high core count machines more representative of performance on low core count machines.
-Jeff On Wed, Oct 28, 2020 at 4:02 AM Gabriele Svelto <gsve...@mozilla.com> wrote: > > On 27/10/20 21:18, Jim Mathies wrote: > > 3) Detect noticeable performance issues with page interaction and scrolling > > that normally don't occur, we'd appreciate bug reports with Firefox > > profiles. > > Is the software fallback expected to use all available CPU cores/threads > for rendering? I enabled it and played around a bit on Google Maps. > Performance is visibly lower than with hardware support - something I > did expect - but I could see only one core being loaded at 100%, the > rest were sitting idle. That surprised me because most software > fallbacks (e.g. LLVMpipe on Mesa) tend to use all available CPU resources. > > So I was wondering if this was a deliberate choice (to conserve power on > laptops maybe?) or if I should file a bug. > > Gabriele > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
