FWIW I have seen delays in JDT's autocomplete functionality when either the workspace, or the JDK/src, is on a networked drive (like a users's network-mounted home drive). Both of these problems were solved by moving the workspace and JDK to a local drive.
The JDK is unlikely to be an issue for CDT but the workspace definitely will. It's worth ruling this out as a possibility.
Alex
Sent from my (new) iPhone
We might have a much larger code base,
building a clean index takes 60min, but we don’t have any issues with
content assist. There must be something else.
Jens.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Toan Pham
Sent: Mittwoch, 17. Februar 2010
22:54
To: CDT General developers list.
Subject: Re: [cdt-dev] Improve
Indexer on large project
What i am more concern
with is lookup time for auto completion, although i've experienced slow
indexing time for my project, > 10 mins. Ctag lookup would be simpler
and faster.
The auto completion feature is almost unusable for large projects.
On Wed, Feb 17, 2010 at 3:59 PM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:
The time to index is independent of the lookup time for auto
completion. Indexing is done as you save files or on import of existing files.
Changing indexing strategies won't help you if the look up is too slow. Unless
our database look up is too slow, but it's built for speed and something like
ctags is likely to be really slow (and highly inaccurate since it doesn't do a
real parse).
Is the content assist always slow or is it in only certain files? If
it's always slow (i.e. in every file in your project), then it points to a
problem in the database. If it's only in certain files, then it's a problem in
CDT's parser used to determine the context of the assist.
Hi,
I am working with a large project and find that the eclipse's indexer takes a
long time (10 secs or more) to look for auto completion tags.
I do not know what happen to it; probably the algorithm for the indexer is
inefficient. I am not sure if anyone has thought of the following methods
to improve performance on intelli-sense feature:
1. Use Ctag database - Having the ability to load a ctag database
(similar to a feature in Ajunta) and index based on the ctag database
only. I can imagine this is a nice must-have feature because it speeds up
eclipse and also making eclipse more valuable.
2. Path Filter indexer - Having the ability to filter out directory paths
that the indexer should not be indexing would also speed things up.
I like eclipse and hope that developers are improving the indexer in any
way. These are my thoughts and hope that they'll consider them.
Thanks,
Toan
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
