New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compare speed by speedometer #640
Comments
Could you tell us more details on the used system (e.g. CPU and which Thorium build has been used, the AVX or AVX2 build)?! Benching different versions against each other could be misleading as there are indeed newer features/optimizations in newer builds that might have a performance impact. Needless to say that also having the same modifications/options enabled in both builds could make a difference. |
As I write on top of the issue, I used deb packages from the official repo. No manual builds. Processor Intel i5-10500H. GPU is Nvidia 3060M (laptop). Enabled additionally only GPU's based rendering. Without it, the result is almost the same. |
As there are several Thorium deb packages from the official repo under https://github.com/Alex313031/thorium/releases/tag/M122.0.6261.132 please specify which one you used. Your CPU should be compatible with the AVX2 build that is available under the given link and should provide the best performance for your system, please test that one if you haven't already. To make a fair comparison, I'd suggest to benchmark Thorium AVX2 and Google Chrome on the same revision and with the same settings/config options. |
Official debian/ubuntu repo.
What's profit of that? Official debian repos provide different versions. Users don't hold a version of Chrome. Currently provided version is good point to comparison. |
Then please test the AVX2 version that is provided under the release link I gave you as I cannot say which compiler flags Ubuntu uses to compile their provided Thorium version and if they honor the aggressive flags used by Thorium by default.
As you haven't noticed yourself yet, you are comparing an "unofficial" Ubuntu-provided build of Thorium which is most likely not using all the capabilities of your CPU properly against a newer revision of Chrome. That's not a fair comparison for these following two most important reasons:
|
OFFICIAL Thorium repository. I wrote "official". And official Google repository. That means we have two providers who give almost the same product. And I am trying to compare them. sudo rm -fv /etc/apt/sources.list.d/thorium.list && \
sudo wget --no-hsts -P /etc/apt/sources.list.d/ \
http://dl.thorium.rocks/debian/dists/stable/thorium.list && \
sudo apt update Ask @Alex313031, which flags he used in his repo. |
I test latest thorium release (123) with AVX2 support (got from latest gh release for the integrity of the experiment) and latest chrome stable release (124). Each browser was run with clear user profile dir (run with
|
@onegreyonewhite You should be comparing identical versions. Using M124 for Chrome is unfair. For example, M123 got a nice speed boost from upstream over M122. So comparing the two would be unfair to the M122 build. |
I don't agree with you, because users uses the latest available version. So now you're behind one version. Users should know current difference in performance. Anyway, now I hold current chrome version and I'm going to wait 124 version of Thorium for the fairest comparing. @Alex313031 you should know that I like thorium. I think you make really useful job. I highly respect you for your work. This is an impartial comparison. |
Hi, everyone! As you can see from the results below, the official Debian packages for Google Chrome often show much better performance. In situations where Google extensions and services are running, you can occasionally see better results with Thorium for older technologies like ES5. However, anything built with more current JavaScript standards shows significant or slight performance degradation. I would look into which rendering acceleration flags can be used. For example, enabling GPU rendering and zero-copy significantly speeds up Thorium compared to Chrome (the tests already include these flags, so the difference isn’t as dramatic without "powered anon"). It might be worth running individual tests to pinpoint where the slowdown occurs and see if it's possible to address it. Additionally, it would be beneficial to focus on more current code porting from Chromium. Yes, this is the most challenging part, but it actually provides the greatest speed boost. Thorium - 124.0.6367.218
Actual versions without access to google account and without any extensions (I call it "powered anon") and same versions: Thorium - 124.0.6367.218
Current available stable versions on ubuntu with google services and enabled extensions: Thorium - 124.0.6367.218
Actual versions without access to google account and without any extensions (I call it "powered anon"): Thorium - 124.0.6367.218
|
Recently, I noticed that official Chrome seemed to render pages a little faster. I decided to take some measurements.
Thorium 122.0.6261.132 (from official repo)
Google Chrome 124.0.6367.60 (from official repo)
Ubuntu 22.04 LTS with all updates.
https://browserbench.org/Speedometer3.0/
Somehow it doesn't look very good. Are these two major versions really packed with so many optimizations?
The text was updated successfully, but these errors were encountered: