Re: optimizing compilers
Re: optimizing compilers
- Subject: Re: optimizing compilers
- From: email@hidden
- Date: Sat, 2 Feb 2002 10:55:43 -0800
I think that the combination of Quartz and broken Cocoa display
semantics is
slow because my company sells a high end vector animation application
that
is much faster on a 266Mhz Pentium PC running Openstep than it is on a
450Mhz G4 running OS-X. I have posted many times on this subject.
Part of
the problem is that the Foundation classes got much slower between
Rhapsody
DR2 and OS-X. Part of the problem is that Quartz vector rendering is
slower
than Display Postscript used to be. We can work around the Foundation
framework problems, but we are stuck with slow (but admittedly more
capable)
Quartz.
I imagine you have benchmarks that support these assertions; but more
to the point, your application is a very special case. I stand by my
assertion that for the typical user who perceives slowness in most
operations on OS X, Quartz is not a factor.
And by default, Quartz does the extra work of antialiasing, which DPS
didn't do. I assume you have turned off antialiasing with
[NSGraphicsContext setShouldAntialias:] for a fair test? Were the bit
depths, hardware acceleration, bus speeds, etc. such that this was a
fair comparison? There are a huge number of factors that play into
rendering that make comparisons like this difficult. It may be the case
that line rendering is slower on the 450Mhz G4 running OS X, while also
being the case that Quartz is running just about as fast as it possibly
could within the parameters of that environment.
Ben Haller
Stick Software