Comments on: ColdFusion Object Creation Performance Hit

By: Reza

Reza — Sun, 23 May 2010 13:08:30 +0000

Hi,

We used iterator pattern to fix this issue, but we used this iterator at cfm pages, I don’t know about Flex.

So inside iterator we converted queries to struct and then during iteration we mapped the values to one cached object.
So it helps us to keep the patterns and also be fast.

By: Steve Brownlee

Steve Brownlee — Mon, 16 Feb 2009 21:11:29 +0000

@dfguy: I haven’t the slightest clue. Are you certain that you are considered a jerk off? How did you come to that conclusion?

By: dfguy

dfguy — Mon, 16 Feb 2009 20:12:48 +0000

why is that if someone else in the community saids that the object performance in CF needs to be addressed, everyone agrees with them. Yet I’ve been making this arguments since cf8 came out and i’m considered a jerk off?

By: Fusioncube > ColdFusion Object Creation - More

Fusioncube > ColdFusion Object Creation - More — Fri, 13 Feb 2009 04:51:56 +0000

[...] up on my original post about ColdFusion performance hits on creating objects – it was suggested that I return an array of typed structures instead of an array of [...]

By: Steve Brownlee

Steve Brownlee — Fri, 13 Feb 2009 04:36:00 +0000

@WilGeno: I’m actually using update 10. However, you’re right that update 10 is faster than update 4 because when I upgraded, I did see a measurable performance gain.

By: WilGeno

WilGeno — Fri, 13 Feb 2009 03:52:03 +0000

First of all your correct that loading of objects (classes) is slower in CF8. Well not technically CF8 but with the Sun JVM 1.6.0_4. There is a known class loader bug that is the cause of this. This is NOT Adobe’s problem it is (or was) Sun’s problem that has been fixed as of the 1.6.0_10 version. I’d be interested in knowing which JVM version your running. If your running the old version try upgrading and run your tests again to see if the problem is reduced or even resolved.

I wrote a blog post ob the JVM versions and which ones you may wish to be using. Here is the link from that post to Sun’s bug report which reports the bug is fixed.

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6566201

By: Brian Kotek

Brian Kotek — Thu, 12 Feb 2009 23:36:58 +0000

David, the build in LiveCycle license is only good for 1 CPU, which pretty much removes it as an option.

To me, the issue of CFC creation overhead is rapidly becoming THE issue facing ColdFusion. If CF9 doesn’t deal with this (and by deal, I mean improve the object creation time at least tenfold), then the additional features like Hibernate integration and Flex integration are going to be virtually meaningless except on very small projects. With options like Groovy rapidly gaining traction, this could really impact negatively on CF. Let’s hope they can pull it off!

By: Steve Brownlee

Steve Brownlee — Thu, 12 Feb 2009 20:26:07 +0000

@phil: yes, I’m creating CFC arrays and sending to Flex – which has matching VOs so that I can have typed objects.

By: phill.nacelli

phill.nacelli — Thu, 12 Feb 2009 20:21:04 +0000

@Brian,

That’s where I was going with my question, the “__type__” value object struct is a huge help when returning multiple objects to Flex. As far as composition goes, I’m playing around with a recursive method for dealing with queries, I do have it working for returning a single CFC with other CFC properties.. and I’m very happy with the speed so far.

Cheers..

By: David Buhler

David Buhler — Thu, 12 Feb 2009 20:07:44 +0000

You can use CF8s built-in LiveCycle to handle pagination.

http://www.adobe.com/devnet/livecycle/designer_scripting_samples.html

If I remember right, there’s pagination for Flex built into CF7+ Remoting, but I haven’t used it in quite some time.