|RE: [cdt-dev] Improve Indexer on large project|
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.
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Toan Pham
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
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.
On Wed, Feb 17, 2010 at 3:30 PM, Toan Pham <tpham3783@xxxxxxxxx> wrote:
Back to the top