Re: Compressing and decompressing pages
Squicky? Why...you mean (egad)...
Monitoring tools will bark at ballooned address spaces being used by these 'compressed memory' processed?
The same for the additional Swap (sorry paging file) being used to orchestrate it?
VMware and other virty 'dynamic resource features will get into race conditions?
That BSODs may be making a comeback where there's no address space left to un-compress?
Clustering will get fecked up?
...or was it something else entirely?
(if this ever makes it to WinServ).