Community
Participate
Working Groups
The "Cache Types in Background" feature that is part of the work in progress sounds like a good idea. The only problem is that I have about 5000 C++ files in total in my workspace and caching takes a long time. Although it says its doing it in the background it is taking up a huge chunk of my CPU causing everything else to freeze and the eclipse java process grows to around about 400MB in size. Is there any way that the priority of the background process can be reduced? Is there any way that the cache could be held somewhere other than RAM?
I also find the type cache to be too intrusive. I have a project with about 2000 files, and the type cache stuff seems to run EVERY TIME that I start eclipse (M8) with CDT (latest from head May 15). This will cause no end of complaints from users with projects that are larger than toy problems. It looks like every file is being parsed on startup (taking large amounts of memory). I thought the whole idea of the indexer was to prevent this from happening??
This doesn't look like it is a problem anymore. The indexer is only involved if the files were not indexed, and the type cache doesn't parse any files. The memory requirements are low, and it is speedy. From my point of view, this defect can now be closed.
Agreed.
