[EMAIL PROTECTED] (Edgar Gonçalves) writes: >> [EMAIL PROTECTED] (Edgar Gonçalves) writes: >> >>> The features look great, but I started noticing my CPU usage going too >>> often to >>> the ninety-ish percent. >> >> Did you check that the CPU usage actually comes from Emacs, or is it >> from a subprocess ? >> >> Emacs is mostly non-preemptive, so when it uses the CPU itself, it >> freezes, and you can't use it before it completes (except if the elisp >> code is using some complex tricks, but I'd be surprised if this is the >> case of DVC). >> >> OTOH, we might well be launching subprocesses in an incorrect way. > > I just rechecked, the only subprocesses that I can see are gnuserv.exe and > ispell.exe (gnus also launches a cmdproxy.exe to use openssl.exe, but I don't > need to use that to see the cpu abuse). Another interesting fact is that emacs > tries to do whatever it is it's doing in idle time, but only emacs-idle time: > if i'm writing, or moving, or typing in the emacs window, the cpu usage come > to > a feasible 5-10 percent. one or two seconds after i click on the desktop, or > another window, emacs fires the turbo mode! Oh, and did I mention that this > turbo mode took my laptop to a burning shutdown a couple of times, already? I > guess the tagline is not meant to be taken literally: "DVC - making your > computer feel HOT!" :) > > What do you think about this problem?
There are some discusssions about a changed implementation of the emacs idle time handling on the emacs-devel list. I didn't follow these discussions in detail. You could look on the gmane.emacs.devel list for details. Since you are running a recent version (2006-08-30 on W2ONE), I assume you are affected by this erroneous emacs behaviour. So I guess you can use an older emacs or try to get a newer one that has this problem already fixed. Stefan. _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
