On Nov 11, 2008, at 10:47 AM, Chris Espinosa wrote: There is no way to disable project indexing, as dozens of Xcode features rely upon it.
To clarify Chris's statement:
You certainly can disable project indexing. However, you can only do it at the Xcode prefs level, not per project.
And as he said, if you do, you will lose features like: symbol syntax coloring, code completion, and refactoring.
On Nov 11, 2008, at 12:54 PM, Steve Mills wrote: can't boot to 10.6 right now...
Discussion of pre-release software on this mailing list is forbidden. If you have questions about pre-release software, please email email@hidden. All I know is that we never used 3.1 because almost every action (opening project, saving a source file, etc) would result in 5 or 10 minutes of disk thrashing. So I looked 3.1 square in the face and went "pbtpttbptbpb", which is too bad because I was looking SO forward to some of the new features.
Have you filed bugs about these issues?
There may be times when it thrashes for you, but it's due to specific aspects of your setup that we don't see on our end. Issues like that won't get fixed unless you file bugs.
On Nov 11, 2008, at 10:47 AM, Chris Espinosa wrote: On Nov 11, 2008, at 8:19 AM, Simon Wilson wrote: While I sincerely appreciate you taking the time to respond to my question in such detail, I'm afraid it wasn't really the kind of answer I'm looking for.
I don't believe the thrashing is abnormal and, while mildly inconvenient, certainly doesn't warrant me investing the time into profiling the issue.
I simply wanted to ask the xcode-users list in the hope that an Xcode developer might popup up and say "yup, that's symbol indexing and you can disable it by ...".
I still live in hope that an Apple employee might chime in...
It's most likely to be indexing. Without forensic evidence, we can't really tell, but indexing is the most disk-intensive background task done by Xcode. Dependency analysis is second, but it just stats the files to check their mod dates, while indexing (obviously) reads the fulltext of files.
Thrashing certainly isn't what we consider to be normal. We can guess what it is, but we don't know. This may be an issue, like I said above, where the only way we'll know to fix it is if we hear from you.
That's probably not what you want to hear, Simon, and of course we can't guarantee anything, but I think this would make for a useful bug.
-- Andrew |