kicad-developers team mailing list archive

["emmedics4" <marco.serantoni@...>]

--- In kicad-devel@xxxxxxxxxxxxxxx, Wayne Stambaugh <stambaughw@...> wrote:
> Dick Hollenbeck wrote:
> > Marco Serantoni wrote:
> >> As was requested, i've done a trivial benchmark, i've taken a file from wxWin tracker and readapted to do a trivial test just to begin to taste the difference of times of the two approaches.
> >>
> >> The test does 100000 lines in a square of 100x100.
> >> For the wxGC 

> See the attachments for the results I got on the same computer to
> compare gtk/cairo performance versus msw/gdi+ performance. I modified
> Marco's program to use a single wxGraphicsPath instead of 10 and removed
> the grid since it was not drawn using wxDC. I thought this might be a
> bit more sensible comparison.  

Good, but no application would use only one Path (means 1 thichness and color), using 10 changes something ?

> Marco's results on OSX are what I
> expected. On OSX wxDC == wxGraphicsContext so Marco's test proves that
> using wxGraphicsPath to do the drawing versus calling DrawLine() 200,000
> times saves a lot overhead.  

I weren't expect that "difference" of performance on absolute time, i've anIntel GMA 950 with 64MB of shared memory.

Looks that overpriced and crap hw also does its work well.

> On gtk/cairo and msw/gdi+ the story is
> different. Although there is an order of magnitude performance
> decrease, gtk/cairo is probably usable. However, the the msw/gdi+
> situation is bleak. I cannot see how msw/gdi+ could ever be made usable
> for Kicad (or anything else for that matter). The msw/cairo combination
> still needs to be investigated. I'll try to test this over the next
> week or two when I get some free time. I may also try to modify the
> example to use SFML if it isn't too much of a hassle to see if it lives
> up to it's name.

Which CAIRO backend are you using and with which driver on linux ?

> It's looking like Manveru was correct about GDI+ performance. It is
> also looking like I may have wasted my time moving the coordinate
> transforms to wxDC if we can't use wxGraphicsContext due to performance.

First test are for NO GO for me too, but better doing more deep tests before thrash all.

--
Marco