[Digikam-devel] [Bug 198063] Digikam startup is extremely slow
Edmon
edmon at laposte.net
Sun Sep 19 19:30:48 BST 2010
https://bugs.kde.org/show_bug.cgi?id=198063
--- Comment #27 from Edmon <edmon laposte net> 2010-09-19 20:30:43 ---
Thanks for your answer Johannes. I still have a question:
Because I disabled the search for new elements at startup, I would not expect
digikam to do any scan at startup. But strace -c gives something similair to
comment #11:
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
40.61 1085.971160 16871 64369 2861 stat64
18.87 504.701133 8906 56672 41793 access
8.78 234.882550 15863 14807 8507 read
4.59 122.687562 16710 7342 767 lstat64
4.55 121.577073 17274 7038 clock_gettime
4.35 116.254236 15736 7388 poll
2.96 79.104965 17974 4401 1960 open
2.54 67.821400 15736 4310 writev
2.07 55.338870 16176 3421 fstat64
1.63 43.579692 17404 2504 close
1.58 42.294013 15572 2716 gettimeofday
1.02 27.192223 19354 1405 getdents
0.95 25.522614 16267 1569 fcntl64
0.89 23.930248 18710 1279 time
0.75 19.972555 18391 1086 mmap2
0.55 14.635050 18502 791 inotify_add_watch
0.46 12.408250 19208 646 statfs
0.41 10.844816 15274 710 42 inotify_rm_watch
0.34 9.191334 17778 517 write
0.29 7.739680 18605 416 mprotect
0.26 6.918042 18063 383 _llseek
0.20 5.441880 17113 318 37 futex
0.21 5.505908 17876 308 brk
0.20 5.225893 17836 293 ioctl
0.16 4.249862 17857 238 16 unlink
0.15 3.996653 18167 220 munmap
0.09 2.312125 18497 125 uname
0.07 1.996904 19201 104 getcwd
0.07 1.785698 18221 98 fchmod
0.06 1.724894 18350 94 link
0.05 1.281683 15442 83 select
0.01 0.384020 19201 20 4 connect
0.01 0.307216 19201 16 shmctl
0.01 0.211211 19201 11 readlink
0.01 0.153608 19201 8 pipe
0.01 0.153608 19201 8 geteuid32
0.01 0.153608 19201 8 setsockopt
0.01 0.134407 19201 7 getgid32
0.00 0.115206 19201 6 semop
0.00 0.115206 19201 6 semctl
0.00 0.096005 19201 5 sched_get_priority_min
0.00 0.076804 19201 4 fdatasync
0.00 0.076804 19201 4 2 mlock
0.00 0.076804 19201 4 sched_get_priority_max
0.00 0.076804 19201 4 ftruncate64
0.00 0.076804 19201 4 getegid32
0.00 0.076804 19201 4 clock_getres
0.00 0.076804 19201 4 shmat
0.00 0.076804 19201 4 shmdt
0.00 0.076804 19201 4 shmget
0.00 0.057603 19201 3 pipe2
0.00 0.057603 19201 3 3 send
0.00 0.038402 19201 2 2 mkdir
0.00 0.038402 19201 2 umask
0.00 0.038402 19201 2 rt_sigprocmask
0.00 0.038402 19201 2 semget
0.00 0.019201 19201 1 execve
0.00 0.019201 19201 1 utime
0.00 0.019201 19201 1 fstatfs
0.00 0.019201 19201 1 sched_getparam
0.00 0.019201 19201 1 sched_getscheduler
0.00 0.019201 19201 1 getrlimit
0.00 0.019201 19201 1 getresuid32
0.00 0.019201 19201 1 getresgid32
0.00 0.019201 19201 1 sched_getaffinity
0.00 0.019201 19201 1 set_thread_area
0.00 0.019201 19201 1 set_tid_address
0.00 0.019201 19201 1 statfs64
0.00 0.019201 19201 1 inotify_init
0.00 0.019201 19201 1 set_robust_list
0.03 0.854447 18180 47 getuid32
0.02 0.632035 18058 35 socket
0.02 0.625633 18959 33 clone
0.01 0.374422 17019 22 getsockname
0.01 0.337706 18761 18 getdents64
0.01 0.336020 16801 20 getpeername
0.01 0.321616 17868 18 rt_sigaction
0.01 0.276015 18401 15 kill
0.01 0.248015 16534 15 bind
0.01 0.248015 16534 15 listen
0.01 0.220814 15772 14 accept
0.01 0.220814 15772 14 getsockopt
0.01 0.136807 15201 9 madvise
0.00 0.049603 16534 3 rename
0.00 0.040802 10201 4 getpid
0.00 0.030402 15201 2 fchown32
0.00 0.015201 15201 1 lseek
------ ----------- ----------- --------- --------- ----------------
100.00 2674.110292 186095 55994 total
Why digikam would call 64369 times stat64 when I disabled the search for new
elements? (and I don't think I have a fingerprint database to look for
duplicates. How can I make sure of that ?)
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Digikam-devel
mailing list