PDA

View Full Version : Microsoft: WARP


GTShotoKen
12-02-2008, 01:16 AM
This week, Microsoft unveiled one of Windows 7’s new features, which will allow games and other DirectX 10 and 10.1-based applications to run fully accelerated on obsolete graphics hardware, and even on systems with no graphics acceleration at all.

Dubbed Windows Advanced Rasterization Platform or WARP, the new graphics layer for Windows 7 will utilize the system CPU as the graphics engine to assist old graphics cards, and take over completely in some cases. Microsoft indicates that WARP will be fully dependent on how powerful the CPU is in a system, but will require one that supports at least SSE2 extensions.

According to Microsoft, even the lowest-end discrete graphics solutions these days are typically 4 to 5X faster than a CPU-only WARP system. Although the performance differences between CPU-only WARP and discrete GPU accelerated graphics is large, WARP offers several advantages: users will still be able to run their 3D applications fully-accelerated when a video card driver is corrupted, missing, or improperly installed/configured. Systems built to take advantage of WARP from a hardware standpoint will be able to display graphics even when the video card is missing—or toasted. So if you’ve nuked your graphics card from a bad BIOS flash, fear not on a WARP-capable system. At least you will be able to boot back up until the video card is replaced.

WARP documentation indicates that the technology will take full advantage of multi-core CPUs and, given today’s technology, Intel’s Core i7 CPU tops the charts.

The following are benchmarks from Microsoft’s own test of Crysis, running at 800x600 with the lowest quality settings:

Crysis on Windows 7 WARP10: CPU Performance
CPU Time Avg FPS Min FPS Max FPS
Core i7 8-Core @ 3.0GHz 271.75 7.36 3.45 15.01
Core 2 Quad (Penryn) @ 3.0GHz 351.35 5.69 2.49 10.95
Core 2 Duo (Penryn) @ 3.0GHz 573.98 3.48 1.35 6.61
Core 2 Duo @ 2.6GHz 707.19 2.83 0.81 5.18
Core 2 Duo @ 2.4GHz 763.25 2.62 0.76 4.70
Core 2 Duo @ 2.1GHz 908.87 2.20 0.64 3.72
Xeon 8 Core @ 2.0GHz 424.04 4.72 1.84 9.56
AMD FX74 4-Core @ 3.0GHz 583.12 3.43 1.41 5.78
Phenom X4 9550 Quad-Core @ 2.2GHz 664.69 3.01 0.53 5.46
Crysis on Windows 7 WARP10: GPU Performance
Discrete GPU Time Avg FPS Min FPS Max FPS
NVIDIA GeForce 8800 GTS 23.58 84.80 60.78 130.83
NVIDIA GeForce 8500 GT 47.63 41.99 25.67 72.57
NVIDIA Quadro 290 67.16 29.78 18.19 79.87
NVIDIA GeForce 8400 GS 59.01 33.89 21.22 51.82
ATI Radeon HD 3400 53.79 37.18 22.97 59.77
ATI Radeon 3200 67.19 29.77 18.91 45.74
ATI Radeon 2400 PRO 67.04 29.83 17.97 45.91
Intel DX10 Integrated 386.97 5.17 1.74 16.22
Notice that Intel’s Core i7 quad-core solution with Hyper-Threading, running at 3.0 GHz, outperforms Intel’s best integrated graphics solution.

According to Microsoft’s WARP documentation:

When WARP10 is running on the CPU, we are limited compared to a graphics card in a number of ways. The front side bus speed of a CPU is typically around or under 10 GB/s whereas a graphics card often has dedicated memory that is able to take advantage of 20-100 GB/s or more of graphics bandwidth. Graphics hardware also has fixed function units that can perform complex and expensive tasks like texture filtering, format decompression or conversions asynchronously with very little overhead or power cost. Performing these operations on a typical CPU is expensive in terms of both power consumption and performance cost in cycles.

WARP Capabilities:

* Fully supports all Direct3D 10 and 10.1 feature
o Fully supports all the precision requirements of the Direct3D 10 and 10.1 specification
o Supports Direct3D 11 when used with FeatureLevel 9_1, 9_2, 9_3, 10_0 and 10_1
o Supports all optional texture formats, such as multi-sample render targets and sampling from float surfaces.
o Supports anti-aliased, high quality rendering up to 8x MSAA.
o Supports anisotropic filtering
o Supports 32 and 64 bit applications as well as large address aware 32 bit applications.
* The minimum specification for WARP10 is the same as Windows Vista, specifically:
o Minimum 800MHz CPU.
o MMX, SSE or SSE2 is *not* required
o Minimum 512MB of RAM.

Clearly WARP won’t be the ideal way to run the latest games. Nor do we expect enthusiasts with Core i7s to also be replacing integrated graphics. Thus, it’ll be interesting to see where Microsoft goes with this feature. WARP will be compatible on both x86 and x64 systems.

Link:

Tom's Hardware (http://www.tomshardware.com/news/windows-cpu-gpu,6645.html)

Z
12-02-2008, 03:12 AM
cool. my interest in W7 has just jumped even higher.

thanks for the update. :)

PS. speaking of graphics, did they actually announce DX11 for 7 or is that coming further down the line?

JasonXe
12-02-2008, 03:14 AM
Interesting...very interesting....

Garfunkel
12-02-2008, 04:10 AM
I've heard things about this recently through MSDN. But I haven't seen those benchmarks. It is indeed very interesting. I love the fact that the CPU can completely take over if need by when the GPU is not functioning for whatever reason. That could have the potential of also giving detailed diagnostic information about the state of the graphics subsystem to the user in a graphical environment, and yet allow them the use of a temporary solution until the issue is resolved.

Now THAT is a type of feature that new OS's should always aspire to achieve, and not 180 bug fixes in a text editor as a 'killer feature'.

One issue however is that it will make the situation more confusing for consumers when buying a certain spec'd machine for gaming.

It is also very interesting that the technology already works with games like crysis, obviously no major changes need to be made to development to allow this functionality, which is always a good thing.

Viper
12-02-2008, 05:17 AM
I agree, Garf. This seems better suited for interim and diagnostic features than as a full time replacement.

Cool feature though if it works well.


Z, DX11 will likely find a home on Vista first (if released that soon and it very well could be) and then on W7. DX11 won't like the jump to DX10 requiring new OS's or GPU's (though DX10 and DX10.1 cards won't have the latest Shader Model) except those still with XP or DX9 cards..

Krad
12-02-2008, 08:17 AM
Very nice news to hear. Haven't read anything about it.

I wonder how advanced it'll be. It'd be nice if I could set a certain % of the CPU to run graphic-related shit on top of my graphics card already.

Xer0
12-02-2008, 08:22 AM
That is pretty cool

Garfunkel
12-02-2008, 10:11 AM
Very nice news to hear. Haven't read anything about it.

I wonder how advanced it'll be. It'd be nice if I could set a certain % of the CPU to run graphic-related shit on top of my graphics card already.

That's what I was thinking, but I imagine that would actually be quite difficult to achieve perhaps. Maybe that will come in version 2.0.

GTShotoKen
12-02-2008, 06:54 PM
I'm personally thinking that this subsystem will work in intel's favor with Larrabee.

Krad
12-02-2008, 09:56 PM
^ Very true. I didn't think about that until your post.


The more options they have for me to take into consideration, the happier I am.

Viper
12-03-2008, 04:30 AM
Won't affect Larrabee at all. This is aimed at surpassing integrated graphics and sustaining 3D rendering during problems and diagnostics, not competing with discreet graphics solutions.

Garfunkel
12-03-2008, 06:06 AM
Won't affect Larrabee at all. This is aimed at surpassing integrated graphics and sustaining 3D rendering during problems and diagnostics, not competing with discreet graphics solutions.

Agreed.

GTShotoKen
12-03-2008, 07:52 AM
Won't affect Larrabee at all. This is aimed at surpassing integrated graphics and sustaining 3D rendering during problems and diagnostics, not competing with discreet graphics solutions.

Well, I just thought it would help Larrabee in some way specifically because it uses x86 cores. Maybe the WARP subsystem can alleviate some of the software rendering headroom Intel has to go through with Larrabee?

Viper
12-03-2008, 03:20 PM
If it helps Larrabee in any capacity, it will likely help all GPU's the same.

Besides, the CPU is already being worked out during heavy 3D acceleration so I doubt you'll tap out more CPU juice using WARP along with a working GPU.....unless the GPU is old or low end.

XboxEvolved
12-10-2008, 03:22 PM
Apple has been working on something similar to this for their next update of MacOSX. It works a little different though I think..