[Pan-users] Re: Filtering unusable slow

[Frederik Himpe]

On Fri, 17 Aug 2007 02:29:03 +0000, walt wrote:

> I've never done any profiling, unlike Charles who has done a lot of it
> while writing pan.  Being ill-equipped for real profiling, I would try
> running pan from gdb and halt it in the middle of those stalls with
> Ctrl-C to see what code is actually running.  If you do that several
> times you should get a feeling for what is taking up all that CPU.
> 
> And don't forget strace (aka systrace) to see if some system call is
> returning errors, etc.

I tried to gather some profiling information. I took the most simple case: 
I start pan, and without doing anything, after a few seconds, I close it. 
It will take a very long time to quit.

You can download a 2.3 MB tarbal on 
http://artipc10.vub.ac.be/files/pan.tar.bz2 which contains an strace of 
this process of more than 40 MB, and also a few gdb traces I gathered by 
running pan in gdb, and Ctrl-C'ing it several times after I quit. I hope 
this helps in identifying the problem.

I am running GNOME 2.19. I would not be surprised if this was related to 
the problem.

-- 
Frederik Himpe