Speeding up ColdFusion Builder
A while back, I wrote a post on Speeding up Eclipse. All of that applies to ColdFusion Builder as well.
One thing I wanted to point out though, which isn't mentioned in the body of that post, is how you can control the Java virtual machine settings for your ColdFusion Builder install. I noticed today when I fired up the CFB public beta that I was getting "java.lang.OutOfMemoryError: PermGen space". I do not think this is a CFB problem per se, but instead attributable to another plugin. This isn't unheard of and is simply what happens when you add more and more plugins to Eclipse. This is NOT heap space.... PermGen is the space reserved for class files. So... more plugins, more classes the classloader has to load.
The good folks at Eclipse realized this problem a long time ago, and you can see this evidenced in the default settings in [eclipse_install_root]/eclipse.ini (at least for the latest Eclipse release). They've set the default permgen size to 256M.
However, it appears that ColdFusion Builder does not have this setting. To remedy that, simply:
Go to your [cfb_install_root]\CFBuilder.ini and open it in Notepad (or any text editor)
At the bottom, add this line:
-XX:MaxPermSize=256m
If you want to tweak the VM even more, you can add all kinds of mysterious options. For example, Here's how I start ColdFusion Builder in a .bat file:
CFBuilder.bat:
"C:\Program Files\Adobe\Adobe ColdFusion Builder\CFBuilder.exe" -showlocation -vm "C:\Program Files\Java\jdk1.6.0_14\bin\javaw.exe" -vmargs -Xmx512M -XX:MaxPermSize=256m -XX:+AggressiveOpts -XX:+UseParallelOldGC -XX:ParallelGCThreads=2 -XX:ThreadPriorityPolicy=1 -Xverify:none
Many of those later settings come from an article by Mike Henke in FAQU some months back.
Enjoy!
Subscribe to:
Post Comments (Atom)

6 comments:
For OS X folks:
Go to your [cfb_install_root]\CFBuilder.app, right-click and choose "Show Package Contents".
You'll find the CFBuilder.ini under Contents > MacOS > CFBuilder.ini
I just upgraded my MBP to Snow Leopard and my Eclipse installation failed to load. I narrowed it down to the -XX:+UseParallelOldGC option. With that option it won't start up, without it it's fine. Not sure what that means, but I thought I'd post a comment here in case anyone else reads this post and later runs into the same problem.
thanks for the update Bob.
Post a Comment