Re: Project as aggregation of other projects. Indexing disabling for such project
Re: Project as aggregation of other projects. Indexing disabling for such project
- Subject: Re: Project as aggregation of other projects. Indexing disabling for such project
- From: Ruslan Zasukhin <email@hidden>
- Date: Mon, 02 Jan 2012 09:49:28 +0200
- Thread-topic: Project as aggregation of other projects. Indexing disabling for such project
On 12/27/11 2:24 PM, "Andreas Grosam" <email@hidden> wrote:
>> "How much of an issue is this in practice?"
>
> Indexing takes CPU cycles. This severely affects wall-time of bench-mark
> programs which for example run in a terminal. This makes running benchmark
> programs unreliable during indexing. Indexing can take up to a few minutes
> even in *small* (whatever this is) projects.
Exactly.
Problem currently is that this first implementation of indexing is far far
not effective.
* it can eat a lots of RAM... On Google you can easy find many posts about
this, and that developers was forced upgrade RAM to e.g. 12Mb to somehow get
back speed
* it have obvious BUGs and LEAKS. I think most of us have see that during
indexing it crashes, or AFTER indexing and next atrempt to make build. Also
easy we can see that RAM after indexing seems to be leaked ... Because if
QUITE xcode after indexing and restart, than build runs faster ...
* SPEED of algs is slow. PROVE is next:
a) our Valentina Studio project could take 60-90 min on CoreDuo2 macs.
So we was forced upgrade all our old harder to i5 / i7 models with at least
8GB of RAM. Not it takes max 4-5 min.
b) Visual Studio MS, and its famous plugin Visual Assist, the same our
project index in few times faster - under minute on comparable hardware. And
when I watch how they do this in status bar ... It seems they use smarter
algorithm to deal once with headers especially with system or libraries
headers ...
c) And the most interesting for me is that BUILD takes much less time
than indexing ...
> Actually, due to this, indexing seriously affects my current development cycle
> where I strive to improve performance of a specific implementation. Whenever I
> make a change in the source, I have to wait a few minutes until the system
> goes idle before it makes sense to run the bench test and get reliable
> results. (for comparison: building takes few seconds).
EXACTLY :-)
--
Best regards,
Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc
Valentina - Joining Worlds of Information
http://www.paradigmasoft.com
[I feel the need: the need for speed]
_______________________________________________
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