Live data from Hacker News

Windows Server 2025 Runs Better on ARM

jasoneckert.github.io

151–156 of 156 posts

Re: Windows Server 2025 Runs Better on ARM

#151
post #143

Earlier quoted context omitted.

How often does software actually ship with the opt in for segment heap turned on though ? Anyway to globally turn it on when a blacklist or denylist or whatever in case something individual acts up ?

Not nearly often enough, because most veteran Windows deverlopers don't even know what segment heap is, or that they have a choice. VS code, for example, is still on NT Heap. It is heartbreaking how under-utilized and under-publicized segment heap is. Raymond Chen needs to make a public service announcement or something. For the question of how to do "segment heap on globally, with a list of exceptions that are still…

Besides better ram utilisation is it offering actual performance improvements (regardless of ram availability) ? Need to read more about this

Re: Windows Server 2025 Runs Better on ARM

#152
post #143

Earlier quoted context omitted.

Not nearly often enough, because most veteran Windows deverlopers don't even know what segment heap is, or that they have a choice. VS code, for example, is still on NT Heap. It is heartbreaking how under-utilized and under-publicized segment heap is. Raymond Chen needs to make a public service announcement or something. For the question of how to do "segment heap on globally, with a list of exceptions that are still…

Besides better ram utilisation is it offering actual performance improvements (regardless of ram availability) ? Need to read more about this

In terms of speed, anecdotally, it seems like it can go either way. Some programs run faster, some run slower. Usage patterns of malloc/free are so varied that it's probably impossible to optimize for one without hurting others.

Re: Windows Server 2025 Runs Better on ARM

#153
post #49

Earlier quoted context omitted.

Even Microsoft considers Microsoft SQL Server legacy! It's had virtually no new features added between 2022 and 2025 other than AI and cloud integration. All the truly capable people have long since left that team and moved into various Azure and Fabric teams. To give you an idea of how bad things have gotten, there's like one guy working on developer tooling for SQL Server and he's "too busy" to implement SDK-style…

> like one guy working on developer tooling for SQL Server As somebody who's been procrastinating on getting my main project off of SSDT, We can all tell.

I wish someone in Microsoft understood how incredibly corrosive to customer trust their new AI-first, cloud-only attitude is.

"We're meeting our KPIs at your expense!"

Re: Windows Server 2025 Runs Better on ARM

#154

I mean we were suspecting for some time that smartphone processors have reached parity with laptop class ones. MacBook Neo proved it. Not clear how both Amd and Intel not only lost the smartphone fight but also lost in their own field (aka servers, laptops, desktops) 15 years ago if I told you that windows would be running better on ARM you would call me crazy.

According to CPU bench, the Neo CPU is about the same speed as a mid range intel laptop CPU from 4 years ago. Apple A18 Pro (Q1 2026): Multithread 11977, Single Thread 4043 Intel Core i5-1235U (Q1 2022): Multithread 12605, Single Thread 3084 -- On the high-end we got i9-13900KS at about 60k, M5 Max 18 scores about the same. But when you move on to server CPUs like Threadripper and EPYC things are about 3x faster. Let…

it's worth noting that the neo is running at 3W compared to 15W for the i5. Just putting an $8 thermal pad on the neo gives you a 20-30% perf improvement by letting it run 5W continuous.

Re: Windows Server 2025 Runs Better on ARM

#156
post #135

Earlier quoted context omitted.

I don't see how this is a 'problem', but rather a tunable. And any decent OS has tunables. Would you rather not have this option?

I would rather have some meaningful progress on the Windows scheduler, for example.

It's doubtful that there would be 1000 people dedicated to the scheduler, or that it would produce a better result than the 1 to 4 people that likely work or are tied to owning the scheduler.

That said, what deficiencies do you see in the scheduler with the current build of Windows?

Post reply on HN