Editing very long ada files with slickedit

[daniel gaudry]

Hi,
while editing the attached file  (recursive descent parser for ada grammar) the screen becomes very slow (selection cut and paste ....).
Even the coloring is slow (10 second).
Any idea?
Best regards*Daniel

[Clark]

Please post your user.cfg.xml. I'm guessing I need your settings.

[daniel gaudry]

Hi
Here is the requested file
Best regards

[Clark]

What are the CPU specs on your machine?

Is there any particular edit that seems to be very slow? Sounds like you are experience slow performance with any editing.

I would recommend turning off "Symbol coloring". It is very CPU intensive. Tolls>Options>Languages>Application Languages>Ada>Appearance.

I'm testing on an LG Gram i7 laptop (2020). Slowest machine I have. I'm only seeing very slight delays (definitely less than 1 second for symbol color coding).

[daniel gaudry]

Hi my machine is recent 32 core amd.
Switching of colors ? not very useful.
I modified a lot of settings and some are more useful that others
the newest attached file works best
Any further ideas

Best Regards

[Clark]

I tried all of the configs you posted. I'm not noticing any difference. Sorry I can't help more.

[Graeme]

Hi

How long have you been using slickedit for?
How long have you been using slickedit to edit this file for?
Do you notice the slowness as soon as you start editing the file or only after a while.

Do you notice slowness on any other files?  If not, try an experiment, copy the top half of the code to another file and see if it's slow there, if not add half of what remains and check again, repeat until slowness turns up.

Does the file belong to a project, if so how big is the project and how big is the tag file?

Last thing to try, run slickedit with a "clean config"  - vs.exe +new -sc some-empty-folder   - then don't open any project, just open the one slow file and see if it's slow.
 

[daniel gaudry]

Hi,
I have used slickedit for quite a few years. It is quite complete (and thus has a sharp learning curve).  Indeed  small files edits very fast . It is just that a recursive descent parser with a large backus naur grammar result in a large code file. Otherwise i will not have done it that way.
The corresponding "beautifier"  is a moderately large project . I attached the current version should you be interested in looking.
In any case, please keep up your good job

Best Regards
Daniel

[Graeme]

I installed V27 beta 2 so that I could try with your project, then I imported your options file.  The huge fonts and icon sizes caused me some problems.  I reset the fonts to something useable for me but I couldn't get rid of the massive font size in menus so it was a little hard to use.  Your symbol colouring seems to slow things down a little bit  - I got some 1 to 2 second delays sometimes but it seemed to be useable.  So then I replicated all of your code a few times over so that the file went from 12000 lines to 440,000 lines.  This didn't really seem to have much effect - it was still useable.  Page up down was a little bit sluggish but still useable.  Scrolling with the vertical scrollbar was super fast.  Copy paste was fine.

What kind of monitor are you using?  Maybe you have a huge display that is contributing to the problem.

I wasn't suggesting that you shouldn't have large files, just trying to figure out why it is slow for you.  Can you suggest how to reproduce the slowness that you're getting?

If you've been working with this file for a while, when did you first notice the slowness?  Did it just get gradually worse as the file got bigger.

[Dennis]

@Daniel

One way to drill down on performance issues is to use Slick-C Profiling. 

    Macro > Slick-C Profiling > Begin Profiling

    [ work for a while, experience the delays ]

    Macro > Slick-C Profiling > Finish Profiling...

    Macro > Slick-C Profile > Save...

This might help you get an idea of where the time is being spent.

Also, do you happen to have Live Errors or Live Diff enabled?

[daniel gaudry]

Hi,
You suggestion worked wonders (even not intended).
I used Slick-C Profiling as suggested, and  behold, the speed went up and now everything's much better:  almost no more problems.
Many thanks
Best Regards to you