> Date: Wed, 11 Oct 2006 22:15:54 +0200 > From: "Peter Tury" <[EMAIL PROTECTED]> > > I found that newer v22 Emacses (I tried: > - patched EmacsW32 vP060914 (=mid September); > - patched EmacsW32 vP060926 (= end of September) and > - unpatched(!) EmacsW32 vU061011(=current CVS)) > are much slower than older ones (I tried for comparison patched > EmacsW32 vP060415 (=mid April)). > > This is recognized with a special mode(?) and big (>200 kbytes) files. > In these cases even C-x k takes several (>5-6) seconds and opening > these files takes even more; it seems to be exponentially worse with > bigger files. Processor load is 100%, 99% is taken by emacs.exe. I > have 200 MB free memory during these steps. > > With old Emacs (I only renamed the directories in Program Files, so > .emacs and every other settings are untouched) everything seems to be > OK. > > My measurements: opening a ~1MB file took more than 5 minutes; killing > it took ~4 > minutes! I realized that if I type something in the middle of this 5 > minutes, it appears at the beginning of the buffer, even if I can see > it only ~2 minutes later (when the content becomes visible). > > For comparison: opening the same 1MB file with patched EmacsW32 > vP060415 (same .emacs and everything) took ~3 seconds; killing it took > ~2 seconds. > > Can you help what to check? What could went wrong?
I don't know what could go so terribly wrong. I use CVS Emacs on Windows XP all the time, and I never get such terribly slow performance. What CPU clock speed do you have on that machine? > How can I check which function takes the processor time? Try the profiling facilities in elp.el. > Have you heard/found similar problems? No, never. _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
