Doh!

I just spent the best part of today trying to work out, what I thought, was a performance problem.

I'm working on an application that kicks off a fairly resource intensive batch process but I was surprised to see RAM being gobbled up at an alarming rate.

So I started a process of commenting out various bits of code until I found where I thought where the problem was occurring. Even testing this piece of code in isolation would still causing memory spikes.

I then remembered how frameworks like model-glue and ColdSpring, call lots of cfc methods which can have a big impact on performance when CF debugging is enabled.

Although I had a cfsetting statement turning off debug output, I still had the overall debug setting enabled in the CF administrator. So changed the setting and hey presto! My system resources are no longer being chewed up.

Brian Rinaldi posted something similar last year:

ColdFusion Debugging Performance Hit