Thanks guys. Even though the site is running on MG1, it's already using CS for all of the DI, so I don't know that I'll get those benefits. Still, I think it's worth doing, and would be a good exercise that I could document as well. I hope to be able to find time to do it. Cheers, Bob
On Thu, Jul 16, 2009 at 12:12 PM, Roy Martin <[email protected]> wrote: > Bob, > > From our experience the biggest improvements came from also updating the > methodology. That is to say MG1 was pretty early on in ColdSpring > development and although it was possible to still utilize it for the most > part all of our model objects were being manually instantiated within the > controller / application. We moved over several large e-commerce sites to > the MG:2 code base, converted all of the objects over to ColdSpring and saw > a huge improvement. On one system that had ~40 objects (model layer code) we > saw the average load time at 400-700 ms in production. Upgrading to MG:2 and > converting them we saw the total load time in production decrease to 75-100 > ms. The total time to upgrade was pretty minimal at about 2 hrs. We have > many less resource intensive sites though that still run MG:1 with 100-200ms > response rates. Word to the wise is make sure that you update all your > controller code to point to the MG2 framework controller as well (what > framework the controller extends). > > Thanks, > Roy > > > > > -- Bob Silverberg www.silverwareconsulting.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
