Yes, "execution time" in Debugging can be very costly in terms of request performance. Thats why I was careful to have debugging turned off.
/cody -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Porter, Benjamin L. Sent: Monday, February 27, 2006 1:30 PM To: '[email protected]' Subject: RE: [Reactor For CF] Performance of Reactor I have noticed that it is not the quickest also on a very robust servers, but this software is still in Alpha so performance tuning probably is not the greatest concern at this time. If you notice any particular areas that seem to be bottlenecks post them up so they can be investigated. I know there should be several performance tweaks possible on the initial factory instantiation in a production mode. One thing that can dramatically slow down pages which use a lot of objects in coldfusion is having reporting execution times enabled in the debugger. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cody Caughlan Sent: Monday, February 27, 2006 2:32 PM To: [email protected] Subject: [Reactor For CF] Performance of Reactor I am using the latest version of Reactor. I have 5 tables (User, Address, Company, Email and Phone) with many-to-many links between User and all of the others. For getting my feet wet purposes I have built a basic no frills page that takes the ID of a given User and display all of their profile information (their address, the company they work for, the company's address, etc). Using the GetTickCount() function and with Reactor in "production" mode and Debugging turned off in CF I the page takes on average 1.5 seconds to execute. Eventually we will be integrating Reactor with MachII, but this basic page is just that, a straight no framework page. I am concerned that with adding the MachII overheard the combo of MachII and Reactor might be a little overboard. For completeness sake I put the Reactor factory in Application scope with its init() so granted this wouldnt be done per-request, and that did seem to save a little bit of time. My question overall is is, how performant is Reactor and are people seeing acceptable production ready speeds with it? Are there any other tricks that can be used to speed up Reactor? I know that it uses lazy-loading and I gave it a couple of requests so that all Record / Gateways / Iterators objects were created, but still couldnt get it less than 1.5 seconds. We have this running on 2 servers (1 for IIS and 1 for MSSQL, both are very beefy, so its not a hardware issue). Previously when we were running MX6.1, basic MachII apps were running slowly. As soon as we upgraded to MX7, those same apps just FLEW (to us it seemed to be a night and day difference). I dont know what relevance this has to Reactor, but just our experiences. Thanks /Cody -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. **************************************************************************** -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
