Well, I updated my MX 7 development box to JRE 1.6.0_18-b07. There was no improvement at all. It's still taking 20-24 seconds to initialize. 40+ seconds after a CF restart. All debugging disabled, CF and MG. If I remove all the event-handlers except the default and the login it initializes in 4-5 seconds, which is what I figured considering I have a couple decent size controllers and model cfcs. MG must be loading a multitude of internal cfcs for each event handler during the loadInitialXMLModule phase.
Crystal Tech also verified that they do have Report Execution Times enabled. I guess that's why it's taking a full minute on their servers. They say (so far) that they're not turning it off. I just assumed they'd have this turned off. I'll probably end up in a battle with them over it, but then I need to get them to upgrade the JRE (good luck). Either way, anything longer than 5-10 seconds isn't going to cut it. I need something that will run on MX 7 in a shared environment for the foreseeable future or it won't be a viable retail product. Unless anyone has anything drastic they can add, I guess I'm going to have to go in a different direction. I'm stumped. Bud -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog 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
