MCU on Eclipse


Home | Pages | Archives


Eclipse Editor Scalability

August 7, 2012 10:26

In Eclipse opening a large file might cause the following dialog:

Editor Scalability Dialog

Editor Scalability Dialog

What does this mean? Well, Eclipse does a lot behind the scenes with source files. And this includes Eclipse Indexer, Outline View or Syntax Coloring.

The drawback of all these great features is: it does not make the Eclipse framework faster. The Eclipse IDE with its Java foundation is in my view the best IDE in the world, but unfortunately not the fastest. That’s why the Eclipse community has implemented settings to keep things within boundaries, and the above dialog is one of this.

As Eclipse tends to get slower and to use more memory for very large files, that dialog warns me about this. I can change the settings pressing the ‘Configure Scalability Settings…‘ hyperlink in above dialog which will open the settings:

Eclipse Scalability Settings

Eclipse Scalability Settings

The same settings are available with the menu Window > Preferences > C/C++ > Editor > Scalability too.  I can configure if I do want that dialog (I usually switch it off), this is the same setting as the check-box on the first dialog. I can change the line number settings to warn me about really big files only.

The warning dialog typically shows up if I open one of the header files containing all the peripheral register declarations, or during debugging if I step into library code.

If performance is a concern, it does not hurt to turn on the scalability mode:

Scalability Mode Turned On

Scalability Mode Turned On

This turns off features which might slow down Eclipse. And there is a price for performance: less functionality.

Happy Scaling 🙂

Posted by Erich Styger

Categories: Eclipse, Tips & Tricks

Tags: ,

7 Responses to “Eclipse Editor Scalability”

  1. I really like your series of article Erich.
    Cheers, Alban

    Like

    By Alban Rampon on August 7, 2012 at 14:21

  2. […] I’m going to have an LED blinking every second. I’m using the TWR-K60N512 with an ARM Cortex-M4 and the Eclipse based CodeWarrior for MCU10.2. But it is easy to adopt it to […]

    Like

    By Tutorial: Timer (LED) with Processor Expert for Kinetis | MCU on Eclipse on August 14, 2012 at 00:00

  3. I have never seen this on my desktop (8GB RAM), only on my notebook (2GB RAM), that explains it. I never read through it, just checked “do not show this message again” and ok, lol!

    Like

    By Karibe on March 1, 2014 at 23:59

    1. I think that might depend as well if it is a 32bit or 64bit operating system too. I have 4 GB RAM and get that message quite often.

      Like

      By Erich Styger on March 2, 2014 at 09:02

      1. I have a 64-bit system

        Like

        By Karibe on March 3, 2014 at 21:16

      2. I set it up for building systems like android community builds( CyanogenMod) but embedded systems won my time

        Like

        By Karibe on March 3, 2014 at 21:41

  4. […] would this be a problem? Well, Eclipse has a built-in limit (Scalability) to avoid indexing files too large and to affect performance. You can see this if you open the […]

    Like

    By FreeRTOS and Eclipse Indexer for >5K Lines Source Files | MCU on Eclipse on October 31, 2020 at 12:25

Leave a Reply



Mobile Site | Full Site


Get a free blog at WordPress.com Theme: WordPress Mobile Edition by Alex King.