I am very surprised with GTK2 having a serious performance problem with
threads.
If that is so I think we should just get rid of the threads completely.
The only reason threads are used for the taps is that I thought it would
give
much better performance.
----- Original Message -----
From: "Olivier Abad"
Sent: Saturday, June 07, 2003 8:55 PM
Subject: Re: [Ethereal-dev] GTK+ 2.2 performance?
> On ven, jun 06, 2003 at 10:58:16 -0500, Gerald Combs wrote:
> > A while back there was a discussion on this list about the GTK2's (lack
> > of) performance:
> >
> > http://www.ethereal.com/lists/ethereal-dev/200210/msg00111.html
> >
> > Since then GTK+ 2.2 has been released. Does anyone know if the
> > performance has improved?
>
> Ethereal built with gtk+ 2.2 is still much slower than with gtk+ 1.2
>
> I think there are two problems :
>
> - rendering performance (probably pango related) : it can have a strong
> impact when opening big capture files ;
>
> - threads : the use of threads in our gtk2 version also has an impact on
> performance (glib/gtk probably uses mutex when threads are enabled
> which explains the slowdown).
>
> I'm not sure we really need threads to update tap listeners : the
> mecanism used with gtk+ 1.2 (gtk_timeout_add) seems to work well enough.
> At least, we could provide a configure option to disable threads.
>
> When opening a file containg 182465 frames with the following filter
> "frame.number == 200000" so that nothing is displayed (to avoid text
> rendering in the GtkCList), I get the following performances :
> - 2'46 for the gtk+ 2.2 version with threads ;
> - 2'05 for the gtk+ 2.2 version without threads.
>
> Olivier
> --
> Marriage is a ghastly public confession of a strictly private intention.
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
