By blitting, we mean copying the contents of one bitmap into other bitmaps. In our test, we copy image clips.
For this test, we copy a total of 50,000 image clips ranging from 1x1 to 500x500 pixels in size, copied to a randomly-chosen position using block level transfer commands (blits). We alternate among the various copying styles, including copy, invert, and paint. As always, the seed for the random number generator is constant so that all test runs produce the same graphics information. And again, all objects are constrained to fit inside the display area, to make clipping unnecessary.
GDI Functions Called
Direct Block Level Transfer commands used:
BitBlt (copy, invert, paint)
Blt commands via the DIB buffer:
Block-level transfers show a general weakness in the Radeon HD 5000-series cards running XP in our tests. For buffered blitting, the Atom almost freezes completely, and the two top-rated cards are nearly unusable when running XP. In this case, both the GeForce GTX 285 and Radeon HD 5870 both perform at the same (poor) level.
- Introduction: Why GDI Output For 2D Graphics Remains Relevant
- The 2D GDI For Windows XP Through Windows 7, In Detail
- 2D Graphics Output Using GDI: Direct Or Buffered?
- The Radeon HD 5000's Symptoms And Their Relevance To Windows 7
- Tom2D: Our Simple 2D GDI Benchmark
- Tom2D: Text Output
- Tom2D: Line Output
- Tom2D Splines/Bézier Curves
- Tom2D: Polygons
- Tom2D: Rectangles
- Tom2D: Ellipses
- Tom2D: Blitting
- Tom2D: Stretching
- UPDATE: ATI Steps Up With A Hotfixed Driver