957
GIMP (credit to mrAnmolv) (lemmy.xylight.dev)
submitted 1 year ago* (last edited 1 year ago) by Xylight@lemmy.xylight.dev to c/linuxmemes@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[-] akash_rawal@lemmy.world 25 points 1 year ago* (last edited 1 year ago)

Everything seems to be way faster on Linux than on windows for some reason.

On one occasion I tested a build that took ~10 min on windows, in a Linux VM installed on the same machine, it finished in ~1min.

I have searched around for an answer for quite some time now, I could not find any definitive reason. Some say that process creation is slower on windows, some say IO is inefficient. Still struggling to explain 10x increase in throughput.

Here is a funny instance: https://emacs.stackexchange.com/questions/17783/why-does-emacs-take-longer-to-start-on-windows-than-on-linux

[-] gosling@lemmy.world 21 points 1 year ago

IMO it's because Windows is targeted for general use so they don't bother optimizing anything. They'll just convince people that thei have aging hardware when things become slow and say stuffs like "unused RAM is wasted RAM" to justify taking up half of my memory on idle.

Even running Linux from a USB is still a way smoother experience than running Windows for me.

[-] akash_rawal@lemmy.world 3 points 1 year ago

Windows is so not optimised (unoptimized?) that I cannot even see what is slow anymore. Doesn't look like windows is targeted for anything in this state.

[-] redcalcium@lemmy.institute 14 points 1 year ago* (last edited 1 year ago)

I thinks it caused by two reasons:

  • process creation has much higher overhead on windows. On top of that, the antivirus system adds additional overhead not present in Linux because it scan every process on launch and monitor its behavior until the process finished. This result in any workflow that relies on launching a bunch of processes (e.g. make-style compilation which launch the compiler process recursively) to be very slow on Windows.
  • file access on windows is also significantly slower on windows due to its filesystem filter. Also, antivirus typically hook into this filter and inspect every opened files. You can imagine this would result in significant slowdown for any workflow that relies on opening a lot of small files (e.g. compilation)

If you disable the antivirus (including windows defender) performance would definitely improve, but it'll still slower than on Linux.

In order to gain sufficient performance in windows, you'll have to use threads instead of processes (basically a single program doing everything instead of chaining multiple program Unix-style) and put your data in a single file so it can load all at once instead of in a bunch of small files loaded recursively. Basically a complete opposite of what people do on Linux.

[-] akash_rawal@lemmy.world 2 points 1 year ago

Thanks for information.

Some day I might try to controllaby worsen process creation and file access of Linux to match windows performance. Not today though.

[-] athlon@lemm.ee 3 points 1 year ago

Well, in case of Gimp for Windows, it also doesn’t help that it uses a modified GTK. So, when you start on Gimp on Windows, the program must load all the GTK libraries first, while on Linux the shared libraries are already loaded.

this post was submitted on 24 Jul 2023
957 points (100.0% liked)

linuxmemes

21340 readers
1673 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS