Coldfusion Builder 1.x performance is dreadful
Related Categories: Adobe, Rants/Raves, Coldfusion, coldfusion builder
After using CFBuilder 1.x (yes I have the update) for sometime now, I'm this close to going back to Dreamweaver CS4 due to CFBuilder's poor poor performance.
After convincing my client to shell out for the IDE, I'm feeling kinda guilty.
I consistently get "(Not Responding)" in the application title bar. My curor goes into an infinite loop of circles and I just wait....and wait...and wait.
It's as if the more files you throw at a CF project, the more it gets bogged down.
I was working swimmingly with CFBuilder in the beginning, with a small project. No problems..everything was copacetic.
Now I had to go out and grab a live site and bring it down to my desktop. Get it working in my local dev environment, then check it into SVN.
First, the FTP client within the app is really slow and buggy. I ended up getting FileZilla and haven't looked back.
Now the project with close to 56gb of code and images to track feels like a tanker ship. I can't go between directories smoothly. The IDE constantly wants to update it's index or something. I have one directory with about 500 image files or more and CFBuilder takes forever to show me the content in it's tree structure. Very Very Very annoying and slow.
I'm going to give CFBuilder a little bit more time before I ask for my money back from Adobe for the sake of my client's bank account.
This is just ridiculous...argh!
Anyone else experiencing anything like this?
1) in windows -- preferences, go to general -- editors -- workspace. Ensure "refresh automatically" isn't checked
2) in preferences, in ColdFusion -- Server Settings, uncheck the "initiate build when" checkboxes for coldfusion builder started, server started, server is added
3) in preferences, in ColdFusion -- Startup, uncheck the two checkboxes
let's see how this works...
Adobe has emailed me saying the issue (more specifically my bug report) was fixed. Unfortunately I no longer work on that very large project and I have not been able to test the performance of the Updater for CFBuilder. I did note that CFBuilder has always worked faster on my Mac Book Pro than it ever did on the Windows workstation at my previous job. Even though my Mac had lesser hardware then the Windows machine. When it comes to SVN indexing there is a very large amount of disk access that happens and I think that the Mac file system is just faster at this than NTSF.
As you find issues like this I highly recommend submitting them as bugs (http://cfbugs.adobe.com/bugreport/flexbugui/cfbugt...), This is the only way Adobe will know about and address these issues. They do communicate and they will eventually send you updates on the bugs. I've received several emails from the CFBuilder team on various bugs I've submitted.
If you want to read more about the issues I was having take a look at my blog.
On my Mac, with the CFB, the activity monitor shows the windowServer up to 100% usage of CPU. That is realy bad hun....