Ivytown will slip into Intel's Xeon E7 chip family
Intel's codenames for processors sound like directions someone might give you if you get lost in the country. Take a wrong turn off of I64 in West Virginia, for example, and you might be told that Ivytown is on the other side of Ivy Bridge, not to be confused with Sandy Bridge. In reality, Ivytown is Intel's codename for an upcoming 15-core Xeon processor based on Ivy Bridge and designed for high-end servers.
For a company trying to reassert its relevance in the cell phone market by going after the high-end smartphone segment, Nokia sure has taken its time getting its E7 out the door. This flagship device is finally available for purchase, provided make your way to Helsinki, Finland or one of Nokia's other flagship stores.
As the system [running Windows Vista SP1] arrived to us, the off-the-shelf configuration had a ~45 second boot time. Performing a clean install of Vista SP1 on the same system produced a consistent ~23 second boot time. Of course, being a clean install, there were many fewer processes, services and a slightly different set of drivers (mostly the versions were different). However, we were able to take the off-the-shelf configuration and optimize it to produce a consistent boot time of ~21 seconds, ~2 seconds faster than the clean install because some driver/BIOS changes could be made in the optimized configuration.
Fortin identifies a number of design goals for Windows 7 to help it achieve a high percentage of "very good" boot times (under 15 seconds), including:
Reducing the number of system services
Reducing the demand that system services make on CPU, disk, and memory resources
Device and driver optimization
Improving parallelism of driver initialization (enabling multiple drivers to be installed at the same time)
Faster prefeching optimized for both traditional and SSD hard disks
Fortin's comments suggest that Microsoft is working very closely with system vendors to help assure that Windows 7 works well in typical preconfigured systems. Hopefully, Microsoft has learned a lot from the vast difference in performance between clean installs of Windows Vista and systems cluttered with OEM products not optimized for Vista.
Don't want to wait for Windows 7 to get faster boot times? Fortin also discusses analyzing systems with the Windows Performance Toolkit for Windows Vista and Windows Server 2008, available here.
How do you define fast boot time? When is a system "ready to go?" Give us your thoughts after the jump.
The Engineering Windows 7 (aka "e7") blog at MSDN is providing us with a useful look at how the performance of Windows 7 is being analyzed in this week's blog post. So, what are the major subsystems being analyzed? Some of them include:
Memory usage: trying to balance time versus space (disk, memory)
CPU utilization: keep it as low as possible to improve multi-user scenarios and reduce power consumption
Disk I/O: reading, writing, paging performance for both traditional and solid-state drives
Boot, Shutdown, Standby/Resume: working with system vendors to make these operations as fast as possible
Base system: balancing "on-demand" loading of resources with the need to keep performance at as high a level as possible
Disk footprint: working with the space demands of device drivers, help system, optional components, diagnostics, and logging information
To learn more about how Microsoft is performance-testing Windows 7, and how your comments can help shape Windows 7, join us after the jump.