[Users] Why scanning takes so long ?
J. Bakshi
joydeep at infoservices.in
Wed Nov 2 17:56:52 CET 2011
Dear list,
I frequently mention that CM has become slow and frozen time to time.
one such incident is "folder scanning" . It takes too much time to scan.....
I have started CM with --debug and collected the log when it frozen during such
scanning. Can anyone give any clue why it taking so long ?
` ` ` `
procmsg.c:1904:Setting flags for message 6 in folder processing
filtering.c:189:checking 7 messages
filtering.c:229:2 messages to move in postfix
folder.c:3668:called inc_lock (lock count 1)
mh.c:249:mh_get_last_num(): Scanning joydeep at infoservices.in/postfix ...
current dir: /home/joy/Mail/joydeep at infoservices.in/postfix
mh.c:1369:MH: forced mtime of processing to 1320249709
msgcache.c:194:Cache size: 6 messages, 2573 bytes
msgcache.c:194:Cache size: 5 messages, 2089 bytes
msgcache.c:172:Cache size: 23441 messages, 12744562 bytes
procmsg.c:1985:Changing flags for message 24102 in folder joydeep at infoservices.in/postfix
procmsg.c:1904:Setting flags for message 1 in folder processing
procmsg.c:1904:Setting flags for message 24102 in folder joydeep at infoservices.in/postfix
msgcache.c:172:Cache size: 23442 messages, 12745046 bytes
procmsg.c:1985:Changing flags for message 24103 in folder joydeep at infoservices.in/postfix
procmsg.c:1904:Setting flags for message 3 in folder processing
procmsg.c:1904:Setting flags for message 24103 in folder joydeep at infoservices.in/postfix
folder.c:3670:called inc_unlock (lock count 0)
filtering.c:226:no more messages to move/copy/del
folder.c:3668:called inc_lock (lock count 1)
` ` ` `
And also some messages are always become marked as new after opening CM.
Cache problem ?
More information about the Users
mailing list