Memory Compression in Windows 10 RTM [video]
channel9.msdn.com
Memory Compression in Windows 10 RTM [video]
1–10 of 22 posts
Re: Memory Compression in Windows 10 RTM [video]
#2My experience on an i4790k machine with 8 GB RAM after "upgrading" to Win 10:
Chrome tabs tend to get swapped out to SSD quite quickly. Re-opening those tabs takes a few seconds now, compared to instantly before. Am pondering adding another 8 GB for a total of 16 to see if it helps...
Re: Memory Compression in Windows 10 RTM [video]
#3If it just weren't "the one hand giveth the other hand taketh away."
I don't use Windows 10 but I read that the uncontrollable updates which take long time are very annoying. Is it really that bad?
Re: Memory Compression in Windows 10 RTM [video]
#4My experience on an i4790k machine with 8 GB RAM after "upgrading" to Win 10: Chrome tabs tend to get swapped out to SSD quite quickly. Re-opening those tabs takes a few seconds now, compared to instantly before. Am pondering adding another 8 GB for a total of 16 to see if it helps...
I have 32GB in my workstation for exactly one app. That app is a browser. It's name starts with C.
Re: Memory Compression in Windows 10 RTM [video]
#5Watched the video the other day, enjoyed it. Note that this already exists in OS X since Mavericks and in Linux since 3.11, although it's not enabled by default on any distro AFAIK (more info: https://www.kernel.org/doc/Documentation/vm/zswap.txt).
Related: I wish Apple did more things like this, videos explaining the internals of the system. The OS X kernel source code is open but you need a deep understanding of Mach and OS internals to understand what's going on. And most processes and services running on the background are closed source and who the hell knows what's going on.
Re: Memory Compression in Windows 10 RTM [video]
#6Watched the video the other day, enjoyed it. Note that this already exists in OS X since Mavericks and in Linux since 3.11, although it's not enabled by default on any distro AFAIK (more info: https://www.kernel.org/doc/Documentation/vm/zswap.txt ). Related: I wish Apple did more things like this, videos explaining the internals of the system. The OS X kernel source code is open but you need a deep understanding of M…
Apple has been very serious about not wanting you to know what's going on in your machine since around 1984. The first Mac needed an extra-long hex wrench to open, a very uncommon tool at the time. They want good developer communities for good apps, yet they don't give them full control.
Re: Memory Compression in Windows 10 RTM [video]
#7Watched the video the other day, enjoyed it. Note that this already exists in OS X since Mavericks and in Linux since 3.11, although it's not enabled by default on any distro AFAIK (more info: https://www.kernel.org/doc/Documentation/vm/zswap.txt ). Related: I wish Apple did more things like this, videos explaining the internals of the system. The OS X kernel source code is open but you need a deep understanding of M…
Apple has been very serious about not wanting you to know what's going on in your machine since around 1984. The first Mac needed an extra-long hex wrench to open, a very uncommon tool at the time. They want good developer communities for good apps, yet they don't give them full control.
I don't know about "not wanting you to know what's going on in your machine." It's more like they want you to treat their public OS API as "the machine": a clean black-box abstraction layer you can build on.
What goes on underneath, while interesting, is not guaranteed to be stable. They might, say, replace x86 with ARM one day, as they already replaced PPC with x86. If you're targeting "the OSX platform", that doesn't affect you; you just hit rebuild in XCode. If you're targeting the underlying computer, you're screwed. Apple doesn't want you to be screwed (really, they don't!), so they try to disincentivize relying on anything below the public API.
Compare this to Microsoft, where the Windows team deals with cases like these[1] by inserting compatibility shims to keep the behavior of applications using undocumented, non-public-APIs (or munging kernel-shared opaque structs, even) stable between OS releases. While it's great for end-users—their apps don't break—it incentivizes relying on private APIs, because Microsoft will effectively keep your app running for you.
[1] http://blogs.msdn.com/b/oldnewthing/archive/2003/12/23/45481...
Re: Memory Compression in Windows 10 RTM [video]
#8My experience on an i4790k machine with 8 GB RAM after "upgrading" to Win 10: Chrome tabs tend to get swapped out to SSD quite quickly. Re-opening those tabs takes a few seconds now, compared to instantly before. Am pondering adding another 8 GB for a total of 16 to see if it helps...
I was running Windows 7 with an HDD and just upgraded to an SSD & Windows 10 because I got sick of listening to my HDD groan for 10 seconds whenever I changed tabs :)
I wonder you're experiencing a use case where you'd see notable perf improvements from a pcie ssd. Jeff Atwood blogged about his upgrade to a faster ssd last week: http://blog.codinghorror.com/building-a-pc-part-viii-iterati...
Of course, assuming you have unused RAM, it would be nice if the OS would just use the RAM available before swapping to SSD.
Re: Memory Compression in Windows 10 RTM [video]
#9If it just weren't "the one hand giveth the other hand taketh away." I don't use Windows 10 but I read that the uncontrollable updates which take long time are very annoying. Is it really that bad?
They aren't that annoying in my opinion since Win10 will ask you to schedule a reboot in advance (within 3 days I think).
Re: Memory Compression in Windows 10 RTM [video]
#10My experience on an i4790k machine with 8 GB RAM after "upgrading" to Win 10: Chrome tabs tend to get swapped out to SSD quite quickly. Re-opening those tabs takes a few seconds now, compared to instantly before. Am pondering adding another 8 GB for a total of 16 to see if it helps...
Today 8GB of ram is a minimum for web browsing, unfortunately :(