Well... didn't get it.
Curious... your performance cut... that would have to include the call to read all the attributes....
Total Performance test.
Caller Code Test.. . start... create object and run init function move record read all columns end
I would be curious if you perform the complete routine if your code runs slower or faster. Would be good for stream lining the code... but this tool is also meant to help the newer CFer who is used to calling recordsets by saying #rsMyData.myColumn# to use my object like #objMyData.myColumn# without having to wrap his brain around doing things yet another way. Keeping things simple and simular where possible. There is a performance hit for creating all the variables every time. (If you call a few MS a performance hit... this tool isn't meant typically for spanning an entire recordset when CFLoop would do... so that comparison is void. This tool is for doing detailed control of a recordset.) If we are talking about a page that executes in 154 ms rather than 124... what type of "performance issues" are you getting?
Again... this tool isn't just about performance of the server. It's also about clean and functional code that isn't excessive in performance cycles. I believe that reading an existing variable is faster than executing a function call to read each varible. It's not something you can simplify to the performance of just one function alone without consideration to how the rest of the code also effects the overall efficiency.
Thanks,
John Farrar
Roland Collins wrote:
Ben,
These are exactly the reasons for my suggestions last night :) Did my revised version of the CFC make it to the list around 10:40-ish? Sometimes they get dropped. It has your suggestions incorporated, and some performance tuning that cuts the iteration time to about 10% of the original.
Roland
---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
