[Shotwell] shotwell with 100k pics: somewhere between quite fast and too slow

[oliver]

On Sun, Aug 14, 2011 at 07:36:55PM +0200, Adam Dingle wrote:
> That's why I recommend sysprof: there's no need to recompile
> libraries, your program runs at normal speed and it's really easy to
> use as well.

Aha, ok. Sounds good. :-)

But it will run without configure's --debug?
(You mentioned that option...)




> I bet that if you install the sysprof package on your
> distribution, you could have it working in less time that the 14
> minutes it takes to start Shotwell with gprof!
[...]

hmhh.


Using -pg and/or -g option I found the problem, that
shotwell seem to hang.

Looked at it with strace, I found the following:

  ======================================================================
  [...]
  clone(child_stack=0, flags=CLONE_PARENT_SETTID|SIGCHLD, parent_tidptr=0x7fffdcc6ac8c) = ? ERESTARTNOINTR (To be restarted)
  --- {si_signo=SIGPROF, si_code=SI_KERNEL, si_value={int=1, ptr=0x1}} (Profiling timer expired) ---
  rt_sigreturn(0x1b)                      = 56
  clone(child_stack=0, flags=CLONE_PARENT_SETTID|SIGCHLD, parent_tidptr=0x7fffdcc6ac8c) = ? ERESTARTNOINTR (To be restarted)
  --- {si_signo=SIGPROF, si_code=SI_KERNEL, si_value={int=1, ptr=0x1}} (Profiling timer expired) ---
  rt_sigreturn(0x1b)                      = 56
  clone(child_stack=0, flags=CLONE_PARENT_SETTID|SIGCHLD, parent_tidptr=0x7fffdcc6ac8c) = ? ERESTARTNOINTR (To be restarted)
  --- {si_signo=SIGPROF, si_code=SI_KERNEL, si_value={int=1, ptr=0x1}} (Profiling timer expired) ---
  rt_sigreturn(0x1b)                      = 56
  clone(child_stack=0, flags=CLONE_PARENT_SETTID|SIGCHLD, parent_tidptr=0x7fffdcc6ac8c) = ? ERESTARTNOINTR (To be restarted)
  --- {si_signo=SIGPROF, si_code=SI_KERNEL, si_value={int=1, ptr=0x1}} (Profiling timer expired) ---
  rt_sigreturn(0x1b)                      = 56
  [...]
  ======================================================================

In one of the runs I had killed shotwell after about 40 minutes via kill(1).

Not sure if this also happens with sysprof.
I may try it, but the mentioned problem should not occure..


Ciao,
   Oliver