The bad full screen performance is without the arcs. It is just one call to fillRect, two to strokeOval and one to fillOval, that's all. I will build a simple test case and file an issue.
On Fri, Mar 27, 2015 at 9:58 PM, Jim Graham <james.gra...@oracle.com> wrote: > Hi Robert, > > Please file a Jira issue with a simple test case. Arcs are handled as a > generalized shape rather than via a predetermined shader, but it shouldn't > be that slow. Something else may be going on. > > Another test might be to replace the arcs with rectangles or ellipses and > see if the performance changes... > > ...jim > > > On 3/27/15 1:52 PM, Robert Krüger wrote: > >> Hi, >> >> I have a super-simple animation implemented using AnimationTimer and >> Canvas >> where the canvas just performs a few draw operations, i.e. fills the >> screen >> with a color and then draws and fills 2-3 circles and I have already >> observed that each drawing operation I add, results in significant CPU >> load >> (e.g. when I draw < 10 arcs in addition to the circles, the CPU load goes >> up to 30-40% on a Mac Book Pro for a Canvas size of 600x600(!). >> >> Now I tested the animation in full screen mode (only with a few circles) >> and playback is unusable for a serious application (very choppy). Is 2D >> canvas performance known to be very bad on Mac or am I doing something >> wrong? Are there workarounds for this? >> >> Thanks, >> >> Robert >> >> -- Robert Krüger Managing Partner Lesspain GmbH & Co. KG www.lesspain-software.com
