Yea, either Reactor is slow, or it's not. Another framework won't make it slow.
Anyhow, the latest patch seems to speed things up. Here's how to get the best performance out of reactor at the moment: 1) Set into production mode. Turn any other frameworks into their equivalent mode. 2) Turn on trusted caching. That's about it. You can add any other techniques you may usually apply. After even more research yesterday I found out that it was my manual aggregation of ratings in the blog that was bogging things down. I changed how that was calculated and the blog flies again. Once again, this wasn't Reactor's fault, but the fault of bad design. Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter J. Farrell Sent: Monday, March 06, 2006 12:06 PM To: [email protected] Subject: Re: [Reactor For CF] Performance of Reactor Brad Haas said the following on 3/6/2006 10:51 AM: > Have you tested Reactor with and without Mach-II? It will be > interesting to see if there is some problem when used in conjunction > with that framework. > I really doubt it would just be "that framework". ;-) More likely that if Reactor had adverse reactions (hee hee) with Mach-II -- it would probably include Model-Glue as well. Talk about allergies... -- Peter J. Farrell :: Maestro Publishing Member Team Mach-II :: Member Team Fusion http://blog.maestropublishing.com Create boilerplate beans and transfer objects for ColdFusion! Fire up a cup of Rooibos! http://rooibos.maestropublishing.com/ -- 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/
