on mon NUMBER aug NUMBER NUMBER NUMBER NUMBER NUMBER anders eriksson aeriksson fastmail fm said i checked on a number of small messages in a big folder NUMBER msgs the delay of the next button has increased considerably NUMBER NUMBER release NUMBER NUMBER msec latest cvs NUMBER NUMBER msec i m not seeing a hit on next a quick just pound on next and watch the wall clock test shows me able to go through NUMBER messages in under NUMBER seconds so it s well under NUMBERms per switch but i m seeing a really piggy cpu spike NUMBER for a few seconds in the flist code of course it seems to be related to number of folders wc mail folders NUMBER NUMBER NUMBER mail folders it s particularly annoying because things just hose and hang for NUMBER seconds so when it hits you have a long latency before what you re doing actually happens NUMBER NUMBER NUMBER background_doperiodic flist NUMBER NUMBER NUMBER flist_findseqs reset NUMBER NUMBER NUMBER NUMBER flistfindstart reset NUMBER active NUMBER NUMBER NUMBER NUMBER reading home valdis mail exmh mh_sequences NUMBER NUMBER NUMBER exmh has NUMBER msgs in unseen NUMBER NUMBER NUMBER NUMBER unseen message in NUMBER folder NUMBER NUMBER NUMBER in flaginner up iconup labelup NUMBER NUMBER NUMBER setting flag glyph to iconup NUMBER NUMBER NUMBER set flag state to up NUMBER NUMBER NUMBER reading home valdis mail list spams mh_sequences NUMBER NUMBER NUMBER list spams has NUMBER msgs in unseen NUMBER NUMBER NUMBER NUMBER unseen messages in NUMBER folders NUMBER NUMBER NUMBER in flaginner up iconup labelup NUMBER NUMBER NUMBER reading home valdis mail trash mh_sequences NUMBER NUMBER NUMBER trash has NUMBER msgs in pseq NUMBER NUMBER NUMBER home valdis mail xemacs NUMBER not found NUMBER NUMBER NUMBER home valdis mail xemacs NUMBER not found NUMBER NUMBER NUMBER home valdis mail xemacs NUMBER not found NUMBER NUMBER NUMBER home valdis mail xemacs NUMBER not found NUMBER NUMBER NUMBER pseq NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER writing home valdis mail xemacs mh_sequences NUMBER NUMBER NUMBER xemacs has NUMBER msgs in pseq NUMBER NUMBER NUMBER flist_done and it takes a hit even if there s no new mail NUMBER NUMBER NUMBER background_doperiodic flist NUMBER NUMBER NUMBER flist_findseqs reset NUMBER NUMBER NUMBER NUMBER flistfindstart reset NUMBER active NUMBER NUMBER NUMBER NUMBER flist_done NUMBER NUMBER NUMBER flist_findseqs end NUMBER microseconds per iteration i m perfectly willing to can opener that code and see where the cpu is going but only if nobody is slapping their forehead and mumbling about a brown paper bag bug valdis kletnieks computer systems senior engineer virginia tech 