Actually, that is not entirely correct. While it is fair to say that CFMX makes use of a just-in-time (JIT) compiler, many people in the industry have a different notion as to what that means. Specifically, a JIT generally is thought to compile code in machine code just in time to execute it. With CFMX, CFML code is compiled into Java bytecode, which is then interpreted by the Java interpreter. A specialized version of the Java interpreter called HotSpot includes a JIT that compiles parts (hot spots) of the Java bytecode to machine code and executes them just in time. Further, VB is not a compiled language; it is interpreted as well.
Matt Liotta President & CEO Montara Software, Inc. http://www.montarasoftware.com/ 888-408-0900 x901 > -----Original Message----- > From: Lewis Sellers [mailto:[EMAIL PROTECTED]] > Sent: Monday, September 09, 2002 3:35 PM > To: CF-Talk > Subject: Re: CFMX - Slow, why? > > On Mon, 9 Sep 2002 16:46:25 -0400, in cf-talk you wrote: > > >I have just finished upgrading my dev box to CFMX. After going through > >a number of issues (search engine friendly URLs, problems with the > >installer), I finally have working sites again - but the debug > >execution times are simply unacceptable. I have 20 apps on this box > >where every page execution was routinely 50 - 500 ms under 4.5 and 5.0. > >Under MX, just about every page takes upwards of 2,000 - 20,000(!) ms. > >I should note this is only the first load of a given page - subsequent > >loads are normal. > > > >Is there some really obvious thing I'm overlooking? Has anyone else had > >this experience? This is a Win2K box with 256MB RAM and a 650mhz > >processor. Again, under CF 5.0 everything ran like clockwork. > > That's the way it is and always is going to be with Java. You'll just > have to get used to it. > > What you're running into is what's called the JIT - the Just-In-Time > compiler. In say a C++ or Visual Basic or even Fortran or Cobol you > compile the source code into machine language specific for a certain > platform once, and then never bother with it again (upgrades not > with-standing.) > > Java's different. Since it's supposed to run on any platform it's not > compiled til it's first called. Thats' what that 20 second delay is -- > your java source code is being *compiled* for the platform it's > currently running on. After that's done once it'll run more or less at > the same speed as say the original C++ version of CF. But anytime you > make a change to any .CFM you're going to take a hit as the CF is > converted into java and the Java's compiled. > > While you're developing you're just going to have to learn to live > with this, Sorry. But it's not so much of a problem on a production > machine fortunately. > > --min > > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
