...which causes frequent BSODs and slow downs in several circumstances (I for one can't enable it without a instant BSOD in the next reboot).
It's disabled by default for a reason, right?
Why do people ever compare it to Windows? Are you trying to justify the money you spent on monopoly while you could have the same functionality for free? You can't justify that.
A FREE product just got BETTER, why the hell some people is offended by that?!?!?! Most will never come close to understand 1% of what was stated! Kernel is not german food FYI!
Is there anything more stupid than "duhhh Windouws has that working for ages now LOL"
Do you people even read the articles? The whole article is about mapped executable paging, not USB 3.0 or Firewire. No, this is not about background/application services, that's something completely different. The kernel mod keeps the core in memory rather than allowing the system to page out parts to disk. It's useful when there's lots of memory available.
The article is about DESKTOP performance and memory use, not portables. It doesn't even hint at the improvement being for hand helds, so obviously the fact they may have limited battery and memory space is irrelevant, otherwise they would be touting those advantages over the existing kernel versions in portable devices.
Buying more memory may not be possible, if you run an embedded handheld device for instance. Some of these devices have only limited RAM available, and putting in more would only suck your battery up faster.
@ BB
Are you referring to the Optimize resources for Background Services or applications setting?? That is nothing at all like what is being done in the Linux Kernel.
Windows can optimize for specific applications or for Background Services but it doesn't try and differentiate code memory or data memory. If application 123 gets paged to disk the memory and data are both as likely to be moved out of ram.
The new work in the Linux Kernel aims to differentiate code from data so only the data gets paged out of RAM.
Obviously you're reading what you want from the statement. Next time assume it's wrong.
Oh and maybe get a better machine if you're seeing BSODs from changing that setting, or better yet, go use Linux to use it.
...which causes frequent BSODs and slow downs in several circumstances (I for one can't enable it without a instant BSOD in the next reboot).
It's disabled by default for a reason, right?
Why do people ever compare it to Windows? Are you trying to justify the money you spent on monopoly while you could have the same functionality for free? You can't justify that.
A FREE product just got BETTER, why the hell some people is offended by that?!?!?! Most will never come close to understand 1% of what was stated! Kernel is not german food FYI!
Is there anything more stupid than "duhhh Windouws has that working for ages now LOL"
SHEEESH!!!
Do you people even read the articles? The whole article is about mapped executable paging, not USB 3.0 or Firewire. No, this is not about background/application services, that's something completely different. The kernel mod keeps the core in memory rather than allowing the system to page out parts to disk. It's useful when there's lots of memory available.
You can enable it in Windows with:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
Set DisablePagingExecutive - 1
@Roger
The article is about DESKTOP performance and memory use, not portables. It doesn't even hint at the improvement being for hand helds, so obviously the fact they may have limited battery and memory space is irrelevant, otherwise they would be touting those advantages over the existing kernel versions in portable devices.
Buying more memory may not be possible, if you run an embedded handheld device for instance. Some of these devices have only limited RAM available, and putting in more would only suck your battery up faster.
Buy more memory. Low memory problem solved..
Better graphics drivers on Linux are good, though.
@ BB
Are you referring to the Optimize resources for Background Services or applications setting?? That is nothing at all like what is being done in the Linux Kernel.
Windows can optimize for specific applications or for Background Services but it doesn't try and differentiate code memory or data memory. If application 123 gets paged to disk the memory and data are both as likely to be moved out of ram.
The new work in the Linux Kernel aims to differentiate code from data so only the data gets paged out of RAM.
Windows NT 3.1 had USB 3.0 support? I hope you understand that USB 3.0 is very new, and even Windows 7 doesn't have built in drivers for it yet.
What is it that NT has had since 3.51 and why is it interesting ?
Interesting how Windows NT has had this since Windows NT 3.51.