JDE/ECB super slow and I don't know what I'm doing... :-(

JDE/ECB super slow and I don't know what I'm doing... :-(

[C. Armour]

Hi EmacsLand,

Please advise.  I recently installed and started using the ECB and
JDE packages.  They're very nice and all that but are they ever

    . . . . . S . . . . . L . . . . . O . . . . . W . . . . .

Obviously, this is unacceptable.  I can't wait two seconds between
hitting a key and seeing the result on the screen.  

How could a person track down what is causing the CPU to spike 
every time I make a minor edit?  When I find out what it is,
then I can disable it.


Not gettin' much work done, I remain,

cda

Re: JDE/ECB super slow and I don't know what I'm doing... :-(

[Eric Ludlam]

The JDE and ECB make use of some cedet tools which install edit
handlers.  One of these handlers could be poking along.

I recommend making sure everything is byte compiled.  There are
several tools using EIEIO objects, and EIEIO classes need to be byte
compiled or they are very slow.

Lastly, you can "M-x toggle-debug-on-quit" and then hit C-g when Emacs
is being slow.  If C-g is enabled, it will tell you what was being
slow.

Eric

>>> cda@milhouse.sgiscpq.com (C. Armour) seems to think that:
>
>Hi EmacsLand,
>
>Please advise.  I recently installed and started using the ECB and
>JDE packages.  They're very nice and all that but are they ever
>
>    . . . . . S . . . . . L . . . . . O . . . . . W . . . . .
>
>Obviously, this is unacceptable.  I can't wait two seconds between
>hitting a key and seeing the result on the screen.  
>
>How could a person track down what is causing the CPU to spike 
>every time I make a minor edit?  When I find out what it is,
>then I can disable it.
>
>
>Not gettin' much work done, I remain,
>
>cda
>

-- 
Eric Ludlam             "Photonic Doodler"    The MathWorks x 7556
eludlam@mathworks.com         (work)        http://www.mathworks.com
eric@siege-engine.com         (home)      http://www.siege-engine.com

Re: JDE/ECB super slow and I don't know what I'm doing... :-(

[Kai Grossjohann]

cda@milhouse.sgiscpq.com (C. Armour) writes:

> How could a person track down what is causing the CPU to spike 
> every time I make a minor edit?  When I find out what it is,
> then I can disable it.

Maybe the elp package is useful.  You could M-x elp-instrument-package
RET (or somesuch), then do what takes time, then M-x elp-results RET
(or similar).

Kai