Intellij Idea 32位与64位速度和性能
目前，我在64位Windows 8.1上使用的是IntelliJ想法14.0.3(之前我使用的是12.1.4).
Currently I am using intellij idea 14.0.3(earlier I was using 12.1.4) on 64 bit windows 8.1.
当我们安装它时，安装程序会在开始菜单和其他位置创建快捷方式，即使在64位系统上，该快捷方式也默认为32位.exe文件.
When we install it, the installer creates the shortcut in start menu and other places which defaults to the 32 bit .exe file even on a 64 bit system.
我知道我可以使用64位可执行文件在此答案中给出的64位模式下运行idea .
I know that I can use the 64 bit executable to run idea in 64 bit mode as given in this SO answer.
但是两个IDE版本之间在性能上有何重大区别?
But is there any significant performance difference between the two versions of the IDE?
对于64位系统，建议使用哪个可执行文件?我应该继续使用32位吗?还是应该切换到64位版本?
And which executable is recommended for 64 bit systems? Shall I keep using 32 bit? or shall I switch to 64bit version?
运行32位和64位启动器之间的区别在于，将使用哪种Java来启动IDE以及传递给它的vmoptions参数是什么.
The difference between running the 32 and 64 bits launcher is which Java will be used to start the IDE and what are the vmoptions parameters passed to it.
启动32位JIDE时，IDEA使用它自己的捆绑式32位JRE.如果没有，则IDEA会尝试按特定顺序(％IDEA_HOME％，％JDK_HOME％，％JAVA_HOME％)在多个位置查找32位JRE. idea.exe.vmoptions中的值将传递给它.
When starting the 32 bit one, IDEA uses it's own bundled 32 bit JRE. If there is no such one, IDEA tries to find 32 bit JRE in several places on specific order (%IDEA_HOME%, %JDK_HOME%, %JAVA_HOME%). The values in idea.exe.vmoptions are passed to it.
启动64位JRE时，它将尝试按特定顺序在多个位置查找64位JRE. idea64.exe.vmoptions中的值将传递给它.
When starting the 64 bit one, it tries to find 64 bit JRE in several places on specific order. The values in idea64.exe.vmoptions are passed to it.
因此，如果要分配2 GB或更多的RAM(使用-xmx)，则32位Java(分别是IDEA)不会发生这种情况.对于使用少于2GB的大型项目，IDE会挂起很多东西.对于较小的项目，我认为您不会有任何不同.
So if you want to allocate 2 GB RAM or more (with -xmx), this is not going to happen with 32 bit Java (resp. IDEA). And for large projects using less than 2GB causes the IDE to hang a lot. For smaller projects I don't think you'll feel any difference.
作为参考，这是关于此的错误，到目前为止，他们还没有采取行动:
For reference this is the bug about this, so far they are not acting on it: