RE: Faster indexing for batch find and project indexer
RE: Faster indexing for batch find and project indexer
- Subject: RE: Faster indexing for batch find and project indexer
- From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>
- Date: Wed, 15 Nov 2006 15:50:33 -0500
- Thread-topic: Faster indexing for batch find and project indexer
The batch finds are converting Doxygen comments from one form to
another. Nothing particularly difficult, but necessary to pass code
review, etc. And I know that the batch find doesn't use the symbol
index; I just happened to be looking at the activity viewer, noticed how
long my find was taking, noticed how long the project indexer was
taking, and started to think up solutions to it. I can easily turn off
indexing, which would ease that problem, but searching still takes a
long time because (I think) the batch find command doesn't build up any
sort of index of the various strings. When I noticed that, and when I
realized that it was very similar to my next project, I wanted to throw
out suggestions for how to speed things up. That's all.
As for searching the source files, well, we have a little over 300 MB of
source + supplemental files, all of which need to be searched through.
Normally, I would just select the files I was going to search over, and
just search them, which would make the find much faster, but I can't in
this case. That is why I'm taking a hit every time I search for
something; I have to search across all of the files, yet again. By
building an index as files are added to the project, and keeping it up
to date as the files are changed (and by updating ONLY those parts that
changed!) I figure that searching can be made faster.
OTOH, if no-one else is seeing the kinds of problems I am, maybe it
isn't a problem that needs solving.
Thanks,
Cem Karan
-----Original Message-----
From: James Bucanek [mailto:email@hidden]
Sent: Wednesday, November 15, 2006 3:05 PM
To: Karan, Cem (Civ, ARL/CISD)
Cc: email@hidden
Subject: Re: Faster indexing for batch find and project indexer
Karan, Cem (Civ, ARL/CISD) wrote on Wednesday, November 15, 2006:
>I've been making a lot of changes in some files (4-500+ at a time) in
>my project to meet our new documentation requirements. This is
>relatively easy to do via the batch find command, but I noticed that 1)
>it takes a lot time to search all the files, and 2) every time I save,
>project indexer gets kicked off, which also takes time.
What kind of batch finds are you doing? The regular text and RegEx
searches don't use the symbols index, so the fact that Xcode is
reindexing should have no impact on your searching beyond competition
for CPU and I/O resources. If you are doing a lot of text or RegEx
searches, simply turn indexing off.
Also make sure you are searching only your source files, and not all of
the headers, frameworks, and so forth. You might want to create a batch
search set just for the source files you are working on.
I find that with enough RAM, most of my source files get cashed prettily
quickly. In a project with over 300 source files, most text and RegEx
searches complete within a couple of seconds (Dual G5, 4GB RAM).
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden