CEDET

Jan Sacharuk <jan@...> writes:

> 2) What sorts of things can I turn off to get a maximal speed improvement?

Don't enable the imenu stuff. It appears to be *very* slow. I only
have the following lines in my .emacs:

  (require 'semantic-load)
  (require 'semantic-analyze)
  (require 'semantic-ia)

  (global-senator-minor-mode 1)
  (global-semantic-show-unmatched-syntax-mode 1)
  (global-semantic-auto-parse-mode 1)
  (global-semanticdb-minor-mode 1)
  (global-semantic-summary-mode 1)

After having inserted these instead of the load-everything command, I
don't think I experience slowdowns anymore.

-- 
Ole Laursen
http://www.cs.auc.dk/~olau/

>>> Ole Laursen <olau@...> seems to think that:
>Jan Sacharuk <jan@...> writes:
>
>> 2) What sorts of things can I turn off to get a maximal speed improvement?
>
>Don't enable the imenu stuff. It appears to be *very* slow. I only
>have the following lines in my .emacs:
>
>  (require 'semantic-load)
>  (require 'semantic-analyze)
>  (require 'semantic-ia)
>
>  (global-senator-minor-mode 1)
>  (global-semantic-show-unmatched-syntax-mode 1)
>  (global-semantic-auto-parse-mode 1)
>  (global-semanticdb-minor-mode 1)
>  (global-semantic-summary-mode 1)
>
>After having inserted these instead of the load-everything command, I
>don't think I experience slowdowns anymore.

There are different levels of Imenu support.  Before writing it off
as a lost cause, look at senator's menu for "imenu config".  There
you will see that you can turn off full directory listings in imenu.
Very large directories can slow that imenu feature down.

Of course, if you don't like the imenu convenience, there is no
reason to turn it on.

Eric

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

"Eric M. Ludlam" <eric@...> writes:

> There are different levels of Imenu support.  Before writing it off
> as a lost cause, look at senator's menu for "imenu config".  There
> you will see that you can turn off full directory listings in imenu.
> Very large directories can slow that imenu feature down.

Hm, I will play with it.

> Of course, if you don't like the imenu convenience, there is no
> reason to turn it on.

Actually, I think the menu is pretty cool - I'm always surprised how
neat the code looks like when properly summarized. Unfortunately, I
never was able to use it for any practical purposes. :-)

-- 
Ole Laursen
http://www.cs.auc.dk/~olau/

On Tue, 06 May 2003 10:15:46 -0600, Jan Sacharuk <jan@...> wrote:

So, nobody has any further advice to tell me what I can do to speed 
anything up? I'm personally inclined to blame WinXP a fair amount for this, 
but these performance issues are really quite bad. I don't want to turn 
EVERYTHING off all together, but it's looking more and more like I'll have 
to. Getting a 5 second delay while trying to move forward through some code 
or modify a variable is really entirely unacceptable.

Thanks,

JS

> Incidentally, it didn't help. I still have odd hang-ups when trying to 
> work. While it's sort of a shame, I'd sort of like to be able to turn off 
> the little tips that show the syntactic construct that you're working in 
> (if, while, whatever) or the class or method that you're currently 
> editing in the command mini-buffer (or whatever it's properly called.)

-- 
Jan Sacharuk
Programmer
BioWare Corp.
jan@...

Hey,

Jan Sacharuk <jan@...> writes:

> On Tue, 06 May 2003 10:15:46 -0600, Jan Sacharuk <jan@...> wrote:
> 
> So, nobody has any further advice to tell me what I can do to speed
> anything up? I'm personally inclined to blame WinXP a fair amount for
> this, but these performance issues are really quite bad. I don't want
> to turn EVERYTHING off all together, but it's looking more and more
> like I'll have to. Getting a 5 second delay while trying to move
> forward through some code or modify a variable is really entirely
> unacceptable.

Did you try turning off the imenu as I suggested? That's not
EVERYTHING. As I said, I had the same problem which went completely
away when turned off the imenu generation.

-- 
Ole Laursen
http://www.cs.auc.dk/~olau/

That's too bad.  I run with most of the goodies turned on with my
poor little 333Mhz processor, and I don't have this problem.

One thing you can try is "toggle-debug-on-quit", and when you feel a
pause, quick hit C-g to see what it is waiting for.  That, at least,
will give us a clue where to start looking.

Good Luck
Eric

>>> Jan Sacharuk <jan@...> seems to think that:
>On Tue, 06 May 2003 10:15:46 -0600, Jan Sacharuk <jan@...> wrote:
>
>So, nobody has any further advice to tell me what I can do to speed 
>anything up? I'm personally inclined to blame WinXP a fair amount for this, 
>but these performance issues are really quite bad. I don't want to turn 
>EVERYTHING off all together, but it's looking more and more like I'll have 
>to. Getting a 5 second delay while trying to move forward through some code 
>or modify a variable is really entirely unacceptable.
>
>Thanks,
>
>JS
>
>> Incidentally, it didn't help. I still have odd hang-ups when trying to 
>> work. While it's sort of a shame, I'd sort of like to be able to turn off 
>> the little tips that show the syntactic construct that you're working in 
>> (if, while, whatever) or the class or method that you're currently 
>> editing in the command mini-buffer (or whatever it's properly called.)
>

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

On Thu, 8 May 2003 23:19:59 -0400, Eric M. Ludlam <eric@...> 
wrote:

> One thing you can try is "toggle-debug-on-quit", and when you feel a
> pause, quick hit C-g to see what it is waiting for.  That, at least,
> will give us a clue where to start looking.

Fantastic. That's exactly the kind of advice I was looking for. I'll try it 
out today. :)

JS

-- 
Jan Sacharuk
Programmer
BioWare Corp.
jan@...

On 08 May 2003 21:47:20 +0200, Ole Laursen <olau@...> wrote:


> Did you try turning off the imenu as I suggested? That's not
> EVERYTHING. As I said, I had the same problem which went completely
> away when turned off the imenu generation.

Oh, yeah. I turned it off a long time ago when the imenu generation was 
costing me five minutes at startup. I have Emacs open all the files I was 
working on when I quit, so the iMenu generation sometimes had to go through 
30 source files. I'm not entirely sure what the imenu stuff does, anyway, 
so I don't really miss it. :)

JS

-- 
Jan Sacharuk
Programmer
BioWare Corp.
jan@...

Hello,

I use emacs GNU Emacs 21.4.1 with the latest cedet suite  & speedbar.
But the performance during editing is devastating.
I have a C++ project with almost 100 cpp files.
1. Emacs is taking ages to start  because it parses every opened file
again and again.
2. When I do editing, emacs freeze for 1 or 2 secs, when i try to save
or even when I move around the edited part
    of the buffer.
3. Deactivating semantic and ecb everything works smoothly again.

My PC is a  Intel(R) Pentium(R) 4 CPU 2.40GHz

and in the .emacs configuration file I have
(setq semantic-load-turn-everything-on t)
(setq semantic-load-turn-useful-things-on t)
(require 'semantic-load)
(setq semantic-imenu-auto-rebuild-directory-indexes nil)
(setq imenu-auto-rescan nil)

(require 'ecb)

(setq semanticdb-project-roots
         (list "~/projects/src/FOO/NBANG"
               "~/projects/src/FOO/PBA"))

What I do wrong and the performance is so bad?

thanks in advanced,
Apostolow

Hi,

  When you turn everything on, some things do slow down.  I recently
wrote a new section in the manual for assisting in tuning semantic for
some environment you could use, and perhaps provide feedback on.

  You can download it from CVS here:

http://cvs.sourceforge.net/viewcvs.py/*checkout*/cedet/cedet/semantic/doc/user-guide.texi?rev=1.24

  It is in the help node called "Speed Debug".  Copy the above file
into cedet/semantic/doc/user-guide.texi of your install area, and then
rebuild the doc.

  Suggestions for improving this section are welcome.

Thanks
Eric

>>> Apostolos Manolitzas <manap@...> seems to think that:
>Hello,
>
>I use emacs GNU Emacs 21.4.1 with the latest cedet suite  & speedbar.
>But the performance during editing is devastating.
>I have a C++ project with almost 100 cpp files.
>1. Emacs is taking ages to start  because it parses every opened file
>again and again.
>2. When I do editing, emacs freeze for 1 or 2 secs, when i try to save
>or even when I move around the edited part
>    of the buffer.
>3. Deactivating semantic and ecb everything works smoothly again.
>
>My PC is a  Intel(R) Pentium(R) 4 CPU 2.40GHz
>
>and in the .emacs configuration file I have
>(setq semantic-load-turn-everything-on t)
>(setq semantic-load-turn-useful-things-on t)
>(require 'semantic-load)
>(setq semantic-imenu-auto-rebuild-directory-indexes nil)
>(setq imenu-auto-rescan nil)
>
>(require 'ecb)
>
>(setq semanticdb-project-roots
>         (list "~/projects/src/FOO/NBANG"
>               "~/projects/src/FOO/PBA"))
>
>What I do wrong and the performance is so bad?
  [ ... ]

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org