Lines Matching full:graphics

14 If you want to generate both the basic system index and the graphics index,
21 the graphics tests) will only run with a single copy.
24 run usually takes about 29 minutes; the "graphics" part about 18 minutes.
26 and dual-processing) and one "graphics" run, for a total around one and
54 tests (currently the graphics tests) will only run in a single-streamed pass.
65 too much.  This is particularly true for the graphics tests.
85    2d              2D graphics tests (not all are actually in the index)
86    3d              3D graphics tests
113     2d-rects         2D graphics: rectangles
114     2d-lines         2D graphics: lines
115     2d-circle        2D graphics: circles
116     2d-ellipse       2D graphics: ellipses
117     2d-shapes        2D graphics: polygons
118     2d-aashapes      2D graphics: aa polygons
119     2d-polys         2D graphics: complex polygons
120     2d-text          2D graphics: text
121     2d-blit          2D graphics: images and blits
122     2d-window        2D graphics: windows
125     ubgears          3D graphics: gears
166     graphics         Runs the tests which constitute the graphics index:
169     gindex           Runs the index and graphics groups, to generate both
209 Graphics Tests
212 As of version 5.1, UnixBench now contains some graphics benchmarks.  These
213 are intended to give a rough idea of the general graphics performance of
216 The graphics tests are in categories "2d" and "3d", so the index scores
218 like a sensible division, since the graphics performance of a system
219 depends largely on the graphics adaptor.
227   detailed diagnosis of an X server or graphics chip, then use x11perf
234 On multi-CPU systems, the graphics tests will only run in single-processing