Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Windows 11's built-in Weather app wastes more than 1 GB of RAM

notebookcheck.net

Post reply on HN
Print view View original

251–260 of 621 posts

Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM

#251

Post by s3p »

rstat1 wrote: post #132
aniceperson wrote: post #128

Earlier quoted context omitted.

1. install ublock origin on Firefox. not even being annoying, edge is removing manifest v2 very soon, breaking proper ad blocks just like chrome

[flagged]

MV3 is severely limited in what it can do. One example that blew my mind is that chrome happily renders webpages immediately after application launch, while extensions are still loading.

Firefox, in contrast, doesn't let the network request fire off to the page until every extension is ready. So chrome is essentially screwing over the user, letting ads/ blocked content load, and intentionally degrading their experience, to make things appear slightly faster.

Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM

#252

Post by benj111 »

hyperhello wrote: post #78
benj111 wrote: post #38

Earlier quoted context omitted.

That still isn't a good look.

I’m not sure if you mean a good look for the process or for the author but paging space is just saying “gimme a gigabyte” like saying “gimme a plate” is at a barbecue. The resources themselves aren’t being used at that point.

As in it's sloppy.

If you're at a BBQ would you take 5 plates just because?

Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM

#253

Post by exceptione »

odo1242 wrote: post #244
danpalmer wrote: post #205

Earlier quoted context omitted.

Apple weather is fully native from what I understand. I suspect the 250MB comes from the video backgrounds they play. Arguably that would be a reasonable thing to sacrifice on low memory systems, you'd barely notice.

I was able to do some tests with AI agent help and got: - ~45 MB on buffers for animated backgrounds - ~10 MB used for the Swift language runtime (runtime type information) - ~44 MB used for system libraries: libSwiftCore, CoreFoundation, libobjc, Metal, VFX - ~21 MB used on GPU buffers (GPU memory is also part of used system memory because of unified memory) - ~6.3 MB for the weatherd daemon that actually collects t…

Relatively optimized? typo?

Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM

#255

Post by kasabali »

vel0city wrote: post #94
Dylan16807 wrote: post #76

Earlier quoted context omitted.

Windows 98 SE kind of went overboard with the graphics (remember Active Desktop?), and a common screen size at the time was 1280x1024. But if you run modern stuff at 1080p (60% more pixels) or 720p ( fewer pixels), you're not going to see comparable memory use.

> and a common screen size at the time was 1280x1024 Maybe if you were really rich and only used high end desktops. A lot of the computers I used back then were still 800x600, fancier ones were 1024x768. If you happened to also have a 2D accelerator card you'd potentially have 1280x1024. And lots of apps purposefully ran at a much lower color depth, it was common for games to run at 8 or 16 bit color mode.

Cheapest local brand 15" CRTs could do 1280x1024 in early 2000s. because you weren't limited by the panel unlike LCDs.

You'd need better than perfect vision to be able to make use of it, though.

Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM

#257

Post by vlovich123 »

inigyou wrote: post #238
glimshe wrote: post #117

Earlier quoted context omitted.

10MB to tell me the weather from a remote server... Let's remember that the sprawling world of Legend of Zelda SNES (a Link to the Past), including all graphics, music, code and dialogue was 1MB.

1MB is about the lowest memory usage you can get on Windows 7, because of reasonable tradeoffs made in the operating system to things like buffer and stack sizes. The OS creates a few threads for you, those threads have stacks and they didn't optimize the allocation size of those stacks - they used a currently reasonable default.

Depends on the app/framework but typically phantom threads don’t get started. Also, those stacks aren’t materialized until you write something - they’re all CoW’ed pages from a sentinel 0-filled page the kernel keeps around just for this purpose.

Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM

#258

Post by colejohnson66 »

Narishma wrote: post #210
SXX wrote: post #192

Earlier quoted context omitted.

Insanity. 4GB was often not enough even back in late Windows 7 era.

4GB is completely fine in Windows 7.

Not to mention that on 32-bit without PAE, that was all you could get. Nothing more.

Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM

#259

Post by ziiinq »

odo1242 wrote: post #244
danpalmer wrote: post #205

Earlier quoted context omitted.

Apple weather is fully native from what I understand. I suspect the 250MB comes from the video backgrounds they play. Arguably that would be a reasonable thing to sacrifice on low memory systems, you'd barely notice.

I was able to do some tests with AI agent help and got: - ~45 MB on buffers for animated backgrounds - ~10 MB used for the Swift language runtime (runtime type information) - ~44 MB used for system libraries: libSwiftCore, CoreFoundation, libobjc, Metal, VFX - ~21 MB used on GPU buffers (GPU memory is also part of used system memory because of unified memory) - ~6.3 MB for the weatherd daemon that actually collects t…

[dead]

Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM

#260

Post by LinXitoW »

david-gpu wrote: post #79
blackhaz wrote: post #73

Earlier quoted context omitted.

10 MB is ridiculously overbloated. 1 MB or something in that vicinity should be more like it.

How much money are these companies going to make by reducing their weather app to 1MB, or 10MB? How much is it going to cost them to get there? The world doesn't run on personal aesthetics, when nobody is willing to pay for them.

Hey, just a few more years of rising memory prices and it'll actually be a marketing term how much RAM something uses.
Post reply on HN