Originally posted by HEL88
View Post
AMD Ryzen 7 7800X3D: Windows 11 vs. Ubuntu 23.04 Linux Performance
Collapse
X
-
Originally posted by Anux View PostIt's about how fast the system responds to user interactions, how fast it boots up (and is actually useable). On my linux box it takes exactly 8 seconds from cold boot (with bios boot time)
Windows reboots every few weeks. And normally you use sleep.
Comment
-
-
Originally posted by HEL88 View PostHmm, 7%.
Linux fans claim that Windows is so slow that it is impossible to work on it.
They claim that on Windows all operations take several times longer and Windows takes all resources and for programs nothing is left.
And it turns out that in the right 28% of the programs Windows is even faster
Comment
-
-
Originally posted by HEL88 View Post
On almost every computer forum there are a handful of Linux fanboys who non-stop write how Windows is bad and how it's slow, how M$ steals everything from Linux and how Windows users are stupid.
Do you feel offended by their opinion?
Comment
-
-
Originally posted by Vistaus View Post
No, but there are other widely used distros like Fedora, openSUSE, etc. and they all have better performance too.
50.56 vs 50.50 geometric mean points.
Comment
-
-
Originally posted by sobrus View PostThe problem with windows is not that it can't run programs quickly. Of course it can. NT kernel is performant and mature and just like Linux it used to run quickly on a 486.
And it's not that Microsoft developers are not talented ones.
I was explaining on Hacker News why Windows fell behind Linux in terms of operating system kernel performance and innovation. And out of nowhere an anonymous...
Windows is indeed slower than other operating systems in many scenarios, and the gap is worsening. The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world.Another reason for the quality gap is that that we've been having trouble keeping talented people. Google and other large Seattle-area companies keep poaching our best, most experienced developers, and we hire youths straight from college to replace them. You find SDEs and SDE IIs maintaining hugely import systems. These developers mean well and are usually adequately intelligent, but they don't understand why certain decisions were made, don't have a thorough understanding of the intricate details of how their systems work, and most importantly, don't want to change anything that already works.More examples:- We can't touch named pipes. Let's add %INTERNAL_NOTIFICATION_SYSTEM%! And let's make it inconsistent with virtually every other named NT primitive.
- We can't expose %INTERNAL_NOTIFICATION_SYSTEM% to the rest of the world because we don't want to fill out paperwork and we're not losing sales because we only have 1990s-era Win32 APIs available publicly.
- We can't touch DCOM. So we create another %C#_REMOTING_FLAVOR_OF_THE_WEEK%!
- XNA. Need I say more?
- Why would anyone need an archive format that supports files larger than 2GB?
- Let's support symbolic links, but make sure that nobody can use them so we don't get blamed for security vulnerabilities (Great! Now we get to look sage and responsible!)
- We can't touch Source Depot, so let's hack together SDX!
- We can't touch SDX, so let's pretend for four releases that we're moving to TFS while not actually changing anything!
- Oh god, the NTFS code is a purple opium-fueled Victorian horror novel that uses global recursive locks and SEH for flow control. Let's write ReFs instead. (And hey, let's start by copying and pasting the NTFS source code and removing half the features! Then let's add checksums, because checksums are cool, right, and now with checksums we're just as good as ZFS? Right? And who needs quotas anyway?)
- We just can't be fucked to implement C11 support, and variadic templates were just too hard to implement in a year. (But ohmygosh we turned "^" into a reference-counted pointer operator. Oh, and what's a reference cycle?)
Comment
Comment