Re: [Gimp-developer] Why is GIMP 1.3.x user interface much slower than 1.2.x?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 24 Apr 2002 15:26:05 +0200, "Sven Neumann" <sven@xxxxxxxx> wrote:
> Raphaël Quinet <quinet@xxxxxxxxxx> writes:
> > Does anybody know what could be the source of these delays?  Is this due
> > to the GIMP itself (debugging code, new user interface) or is this due to
> > the fact that the CVS version uses GTK+ 2.0 instead of GTK+ 1.2.x?
> 
> Hard to say. It's been said that GTK+-2.0 is substantially slower than
> 1.2. I don't notice much difference here but then my machine is
> probably fast enough. Have you played with testgtk; do you notice the
> same problems there?

Yes, I have played with testgtk in both versions.  Unfortunately the
interface has changed so it is hard to compare the performance in both
cases.  The new one from GTK+ 2.0 is definitely slower, but it is
difficult to say if that would explain the difference seen in the GIMP.

Maybe I need to find an even slower computer than my PC at home, so
that I can compare how fast GTK+ 2.0 redraws its widgets compared to
1.2.x.

> Since we use a model-view concept in GIMP-1.3, we use a lot of signal
> emissions to synchronize the UI with the core data structs. You could
> get a noticeable speedup by compiling glib without debugging (default
> since 2.0) and make sure that app/core/gimpmarshal.[ch] is generated
> using a recent version of glib-genmarshal.

Yes, I also get glib and gtk+ from anonymous CVS (updated during the
week-end) so I should have the correct version.

> For further optimizations we should do some profiling first since it
> doesn't make sense to remove useful debugging code unless it shows up
> significantly in the profile.

Of course!  It is much too early to remove the debugging code from CVS
HEAD and it would be foolish to start optimizing anything before the
code is reasonably stable.  And, as you pointed out, no optimization
should be attempted before having a good profiling report.  I was not
trying to find a way to improve the speed of the current GIMP 1.3.x
(not yet, at least), but I was curious to know if anybody had an idea
about what was making it so slow.

-Raphaël


[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux