为什么 Xcode 4 代码完成速度很慢？
有什么办法可以让代码完成反应更快吗？
我在配备 4GB RAM 的 mac mini 2010 和 iMac 21.5 i3 2010 上也遇到同样的问题。
我需要设置一些东西才能使其运行得更快吗？或者只有我有这个问题？
有人有同样的问题吗？
Is there anything to do to make code completion react faster?
I have the same issue on mac mini 2010 with 4gb Ram and on iMac 21.5 i3 2010.
I there something to set to make it work faster? or is just me that I have this problem?
Does any one have the same issue?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我已经开始遇到同样的问题。刚开始还好，但时间长了就开始嘎嘎作响。特别糟糕的是在代码完成对话框打开并且它试图赶上时删除。有人知道可以关闭什么以加快速度吗？
我最近添加了 Accessorizer，所以这可能与此有关。将尝试并更新这篇文章。
我使用的是 MacBook Pro Core Duo 2.4GHz、8GB 内存和 256GB 关键 M4，所以应该没问题！相比之下，Eclipse 运行得很好。
I have started to experience the same issue. Initially it was fine, but over time it has begun to chug. What is particularly bad is deleting whilst the code completion dialog is open and it's trying catching up. Anyone know of anything that can be turned off in order to speed this up?
I have recently added Accessorizer, so it could be something to do with that. Will experiment and update this post.
I'm using a macbook pro core duo 2.4ghz with 8gb ram and 256gb crucial M4, so should be no problem there! Eclipse in contrast runs nicely.
Xcode 4.5 在很多方面都快了一些，包括自动完成，但这仍然是一个问题。有时，当一个项目真正开始出现问题时，我会强制它删除“派生数据”，这将导致 Xcode 重新索引项目中的所有文件。在那之后，有一段时间，事情似乎变得更快了。
要删除“派生数据”，请单击 Xcode 右上角的
Organizer图标。然后在 Organizer 窗口中，单击
Projects选项卡，然后单击派生数据行，单击删除...。执行此操作后，等待大约 5-10 秒，Xcode 应该重新启动其索引。Xcode 4.5 is a bit faster at various things, including auto-complete, but it's still an issue. Sometimes when a project really starts to chug I will force it to delete 'derived data' which will cause Xcode to re-index all of the files in the project. After that things seem to be quite a bit faster, for awhile.
To delete 'derived data' click on the
Organizericon at the top-right corner of Xcode.Then in the Organizer window, click the
Projectstab, then on theDerived Datarow, clickDelete.... After you do this wait about 5-10 seconds and Xcode should restart its indexing.