Path: utzoo!attcan!uunet!aplcen!samsung!usc!snorkelwacker!bloom-beacon!lupine.UUCP!klein
From: klein@lupine.UUCP
Newsgroups: comp.windows.x
Subject: Re: XCopyArea pixmap to pixmap: why is it so slow ?
Message-ID: <8912071944.AA00730@ramona.ncd.com>
Date: 7 Dec 89 19:44:30 GMT
References: <8912060116.AA09564@hpcvxhp.HP.COM>
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 20

> keith@expo.lcs.mit.edu (Keith Packard)
> Because most benchmarking programs only measure performance for
> on-screen graphics, vendors typically optimize the code/hardware which draws
> there, and leave the off-screen rendering to some first-year engineer.

  You respond:
   Hmm, I always thought we optimized the on-screen rendering because it
   had the greatest impact on the usability of the system. 

From what I have seen over the past year here, you gain at least as
much, if not more, "usability" by looking at other parts of the code.
For example, bring up an xmh window with lots of folders, (i.e, lots of
"buttons"), then resize it, move an opaque window over, or just
anything to make it "re-calculate". Beyond a reasonable on-screen
performance level, you can make this *lots* faster by improving other
parts of the server!

Doug Klein
NCD
klein@ncd.com