Robert Hensing, a security engineer at Microsoft, wrote on his blog about a performance flaw in ReadyBoost which severely hindered the responsiveness after resuming from standby (S3) or hibernate (S4) due to an architectural bug. The problem causes irregular and unnecessary hard-disk thrashing after resume which can take up to 8 minutes to settle down - ironically the outcome is the exact opposite of ReadyBoost’s purpose to increase responsiveness by caching. The cause is a simple yet stupid oversight in the design of ReadyBoost’s security system which encrypts all cache-data with an AES-128 encryption key, a great idea badly implemented.
|