how to speedup AppCode

Hi,

i would like to ask you strategies to make AppCode more responsive. I'm interested in software tweaking only. For example changing target requires a new indexing that takes more than 15 seconds. The same is if I switch to simulator from device. Sometimes I experience lag in typing or in finding a class using CMD+O.

These are my settings:

      <key>VMOptions</key>
      <string>-XX:CompileThreshold=100  -Dsvn.keep.connections=false -ea -Xverify:none -Xbootclasspath/a:../lib/boot.jar</string>


      <key>VMOptions.i386</key>
      <string>-Xms128m -Xmx512m -XX:MaxPermSize=250m -XX:ReservedCodeCacheSize=64m -XX:+UseCodeCacheFlushing</string>


      <key>VMOptions.x86_64</key>
      <string>-Xms512m -Xmx1536m -XX:MaxPermSize=350m -XX:ReservedCodeCacheSize=64m -XX:+UseCodeCacheFlushing -XX:+UseCompressedOops</string>


I have 4 giga on the Mac.
Any help/suggestion is appreciated

giampaolo

6 comments

Indexing on configuration switching cannot be improved by changing VM options.
We suggest you to try the AppCode 2.0 EAP build where this problem has been fixed (http://blog.jetbrains.com/objc/2012/12/appcode-2-0-early-access-program-is-open/)

0

You can also try running AppCode in 32-bit mode (right-click on AppCode.app, Get Info, check 'Run in 32-bit mode') - it will consume ~30% less memory.

0

@Anton : at your suggestion, for similar reasons i am now EAP 2.0. Editing software modules > 500 lines is still a royal pain in the neck, with momentus delays at every important keystroke and significant delay at EVERY keystroke. Not holding my breath but will try the next build.

0

Yves,

before suggested the EAP we have warned your, that it has performance problems, that we aware of and tat is already fixed, but not yet released. The point was to make sure that problem with imports, reported as unresolved, has been fixed in it.
We try to make the EAP builds as stable as possible, but such problems may arise periodically; so it's up to you to decide whether to use EAP builds in your development or not.

As for the problem that Giampaolo referenced, it is not related to delays in the editor, but to run configuration switching; and it has, indeed, been fixed in the EAP.

0

I stand edited, but so should you : from the original post " Sometimes I experience lag in typing or in finding a class using CMD+O."  . It is fair to say however that the EAP is (in its current version) slightly faster than 1.6.4. Thus my remark, 'waiting for the next build'. btw , in 32 bits, memory footprint is not all that different for me at the moment.

0

All issues I reported are related to 1.6.3. Including type lag. I showed VM options to show that probably I have enough memory to avoid wild garbage collections.

giampaolo

0

Please sign in to leave a comment.