[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Improve Indexer on large project
|
How many sources, headers, declarations and references does indexer report in the error log after you run Index -> Rebuild on your project?
-sergey
On Wed, Feb 17, 2010 at 2:14 PM, Toan Pham
<tpham3783@xxxxxxxxx> wrote:
My project is 90M in total source file size. Currently i am trying to use vim to take an advantage of its auto-completion and identifier/declarative drill down. I am thinking of getting an I7 920 processor to see if eclipse can performance better; but again, I believe there are many other users out there who are suffering from eclipse performance.
On Wed, Feb 17, 2010 at 5:03 PM, Sergey Prigogin
<eclipse.sprigogin@xxxxxxxxx> wrote:
How large is your project? Auto completion works just fine for me on a project with ~5K files.
-sergeyOn Wed, Feb 17, 2010 at 1:53 PM, Toan Pham
<tpham3783@xxxxxxxxx> wrote:
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.
Doug.
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
_______________________________________________
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
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
