I had added it to a test task sequence last week, just to confirm it didn't blow anything up. Then I added it to my main task sequence, and timed an OSD without the changes, and then with the changes. Unfortunately, there was virtually no difference.
On Tue, Apr 7, 2015 at 10:17 AM, Bain.John <[email protected]> wrote: > 20%-50% seems like quite speed jump … I’d be interested to see some > benchmarking. Is it the decompressing of the wim that receives the speed > buff ? > > > > John > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Keith Garner (Hotmail) > *Sent:* April 3, 2015 5:29 PM > *To:* [email protected] > *Subject:* RE: [MDT-OSD] Speeding up OSD process > > > > This should bump up the CPU performance for SpeedStep processors, and > since WIM decompress/compress uses the CPU, that’s where the performance > gain happens. > > > > However, it shouldn’t speed up disks, memory, network, or the CPU within > virtual machines. > > > > -k > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Miller, Todd > *Sent:* Friday, April 3, 2015 11:07 AM > *To:* [email protected] > *Subject:* [MDT-OSD] Speeding up OSD process > > > > There is an intriguing post on The Deployment Guys about setting the > powercfg to High Performance during OSD that claims to improve writing the > WIM to disk performance by 20%-50%. I can’t wait to try it, and I thought > others might be interested too. If you implement it, please report back on > your time savings and I will do the same. > > > > > http://blogs.technet.com/b/deploymentguys/archive/2015/03/27/reducing-windows-deployment-time-using-power-management.aspx > > > > I got notified of this post on account of following Ben Hunter on the > twitter. > > > ------------------------------ > > Notice: This UI Health Care e-mail (including attachments) is covered by > the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is > confidential and may be legally privileged. If you are not the intended > recipient, you are hereby notified that any retention, dissemination, > distribution, or copying of this communication is strictly prohibited. > Please reply to the sender that you have received the message in error, > then delete it. Thank you. > ------------------------------ >
