Arch Linux User Repository

This package now uses the SSE3 version because benchmarks on my computers show no performance benefit from using the AVX/AVX2 versions.

I made alternate PKGBUILDs: SSE3, AVX, AVX2. (makepkg -p PKGBUILD.avx2)

However, there is no point making dedicated packages for each because there is no performance benefit from using different versions.

The "normal" version ("AVX") does reference avx2 in the config, but the exact compiler flags are unspecified. All 64-bit versions contain AVX and AVX2 instructions. So too do the Chromium binaries from the official Arch repos. Chromium-based browsers probably detect processor capabilities at runtime, so attempting to target specific instruction sets would not be expected to significantly improve performance.

Here are my results from browserbench.org speedometer 2.1, using fresh profiles:

• SSE3: 83.8±1.0
• AVX: 83.8±1.0 (not a mistake, SSE3 and AVX had identical results)
• AVX2: 83.6±1.9

• This is an autoupdating package that attempts to download and package the latest version available.

  • Rebuilding should be sufficient to package new releases.
  • Check that there is actually a new release at Alex313031/thorium.
  • To make the declared version, set environment variable _autoupdate=false

• Avoid flagging and commenting at the same time for the same issue.

  • Flag for common issues with standard solutions.
  • Comment for issues requiring explanation or debugging.
  • Use a pastebin for blocks of text more than a few lines.

I made alternate PKGBUILDs: SSE3, AVX, AVX2. (makepkg -p PKGBUILD.avx2)

However, there is no point making dedicated packages for each because there is no performance benefit from using different versions.

The "normal" version ("AVX") does reference avx2 in the config, but the exact compiler flags are unspecified. All 64-bit versions contain AVX and AVX2 instructions. So too do the Chromium binaries from the official Arch repos. Chromium-based browsers probably detect processor capabilities at runtime, so attempting to target specific instruction sets would not be expected to significantly improve performance.

Here are my results from browserbench.org speedometer 2.1, using fresh profiles:

• SSE3: 83.8±1.0
• AVX: 83.8±1.0 (not a mistake, SSE3 and AVX had identical results)
• AVX2: 83.6±1.9

can we have avx2 version too https://github.com/Alex313031/Thorium-Other/releases

@ugjdgdto Please remove the links.

Users who are uncomfortable with the image can simply not view it.

@Everyone Please do not post anymore comments that have nothing to do with packaging. Fake controversy belongs elsewhere.

[deleted]

The link just shows some "interesting" artwork. There's nothing wrong with it. Even for people who don't care for it, there are worse things on the interwebs to accidentally stumble onto.

Do not visit chrome://theme/IDR_PRODUCT_YIFF in this browser...

Worst mistake of my life.

@direc85 I haven't seen that problem. Have you tried running in a terminal to see if any useful messages are displayed when it occurs?

My computer hard locks whenever I close Thorium browser. Anyone else with the same issue? Manjaro KDE here on 11th gen Intel with integrated graphics here.

I've added processor checks to the post-install and launcher scripts. If the processor does not support x86-64-v3, a warning message will be shown. If the processor supports x86-64-v2, aur/thorium-browser-sse3-bin will be recommended.