There's been a few concerns locally about the move to MX and the hit on COM performance. Especially since the official performance information from Macromedia idicates that COM object instantiation can take up to 10x longer than CF5. Before you ditch the idea of upgrading to CFMX there are a number of things you might try to get COM objects performing at an acceptable level.
Since CFMX now runs on top of a Java J2EE application server there is no longer a direct connection between CF and COM. You necessarily have to go through a Java-COM bridge.
For more information see the J-Integra document site
This can lead to much longer instantiation times for COM objects. This is the time taken to createObject() and not the time for each method call. But you need to check this for your COM object as it may not be that much slower - depends on your environment.
That said, the stats are quoted for CFMX out of the box. There are a variety of things that can be done to improve COM performance:
- put the COM object in a persistent scope
- create a specific java stub for your object
- upgrade the JVM to v1.4 (CFMX ships with 1.3)
The following articles may be of use:
- Using Application Scope to improve COM Performance
- Accessing Complex COM Objects in ColdFusion MX using Java Stubs
- Helpful notes on upgrading the JVM
Only thing you can do is test the COM object in your environment. Don't forget to check that some internal CFMX functionality doesn't already do the job. Not to mention there might be a Java class that already has the same features as the COM object you are trying to integrate.
Hope that helps someone.
Posted by modius at 12:40 PM | Permalink
Trackback: http://blog.daemon.com.au/cgi-bin/dmblog/mt-tb.cgi/51
