Hmmm, I just went to doughughes.net and clicked on the "Cold Fusion"
category - it took quite a long time to load, 40 seconds.  To be scientific,
I tried this from 3 different computers running with 3 different DSL
providers and the results were the same.  I tried other categories as well;
the small ones load at decent speeds, but the larger catgeories take a
*long* time to load.  Am I missing something here? 


Gary

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug
Hughes
Sent: Monday, February 27, 2006 2:12 PM
To: [email protected]
Subject: RE: [Reactor For CF] Performance of Reactor

I'm using reactor on a number of sites and I'm not seeing speed problems.
(See doughughes.net).  I know others are seeing acceptable speed too.

If you have reactor in the application scope are you sure it's actually
running in production mode?  If you had it in development mode and put it in
the application scope, it wouldn't pick up changes to production mode unless
you reloaded the application.

You'll also see a nice speedup with trusted caches turned on.  I'm not using
them on doughughes.net.

If you could dig into the reactor code and determine where the speed
problems are, it would be most helpful.

Doug

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cody
Caughlan
Sent: Monday, February 27, 2006 3: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/



 

-- 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/


Reply via email to