[Bug awt/26486] Graphics.fillRect extremely slow

[fitzsim at redhat dot com]

------- Comment #21 from fitzsim at redhat dot com  2006-03-09 22:23 -------
Please disregard the numbers in Comments 18 and 19.  Because of a bug in GNU
Classpath's build machinery (PR 26623), I was testing the same patch both
times.  Here are the actual results for GCJ:

Flush after every graphics operation:

$ ./FillRect2 
paintComponent took 425 msec. (4097 fillRect calls)
paintComponent took 403 msec. (4097 fillRect calls)
paintComponent took 389 msec. (4097 fillRect calls)
paintComponent took 371 msec. (4097 fillRect calls)
paintComponent took 375 msec. (4097 fillRect calls)
 generation= 100 iterations/sec= 41.1522633744856
paintComponent took 371 msec. (4097 fillRect calls)
paintComponent took 372 msec. (4097 fillRect calls)
paintComponent took 370 msec. (4097 fillRect calls)
paintComponent took 387 msec. (4097 fillRect calls)
paintComponent took 371 msec. (4097 fillRect calls)
paintComponent took 401 msec. (4097 fillRect calls)
paintComponent took 372 msec. (4097 fillRect calls)
 generation= 200 iterations/sec= 41.52823920265781
paintComponent took 373 msec. (4097 fillRect calls)
paintComponent took 389 msec. (4097 fillRect calls)
paintComponent took 374 msec. (4097 fillRect calls)

- oneslime.net hardly flickers at all but feels sluggish.

Rate-limited flushing:

$ ./FillRect2 
paintComponent took 18 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 9 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 9 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)

- oneslime.net flickers badly but is fast and playable

No flushing:

$ ./FillRect2 
paintComponent took 10 msec. (4097 fillRect calls)
paintComponent took 9 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 9 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)
paintComponent took 8 msec. (4097 fillRect calls)

- oneslime.net is unplayably choppy

I don't observe pauses in GameOfLifeAWT on GCJ.

I think these results are pretty conclusive.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26486