A friend reported something odd when they migrated from CF5 to CFMX w/latest updater installed. The application is dramatically slower on MX than on CF5. Nothing seems wrong on the box itself, but the machine hosting the SQL Server database shows unusually high CPU cycles. (mid-to-high 80% - MX - 20-30% in CF5.) This same setup runs fine when using CF5. Anyone seen this before?
Archived Comments
I run a couple of websites currently that are on CF5, I tried to upgrade and had the same problem, had to back track. Would love to hear a possible solution.
We had similar problems like yours. What we did:
1 - Make sure the file jrunresources.xml has the right entries for the datasources.
2 - Updated the class driver to the latest one provided by Macromedia.
I believe the recent Updater contains the latest Database Drivers?
cached query settings? If the increased activity is on the db server, it's gotta be making more calls or making them in a different way.
There is a datasource migration issue that will basically disable the use of indexes on varchar columns.
Tech note here:
http://www.macromedia.com/s...
My suggestions would be:
1) ensure he's on the august updater of 6.1 as there are new data direct drivers in there.
2) open sql profiler, isolate the databases that the datasources are hitting and monitor activity and CPU. Particularly pay attention to CPU,reads,writes columns in profiler.
3) isolate what pages are hit if any when CFMX starts, maybe point the webserver at a directory with nothing in it, again this would probably come from watching profiler to see what sql is being executed.
I ran into this issue before and figured it out.
First off you should make sure that you have "maintain database connection checked" in the datasource in CFAdmin.
Next, check to see what queries are running slow and optismize them. My problem was that for some odd reason a view that I hit slowed the server down to a crawl on CFMX. However, on CF5 it ran like a champ.
I put the view into Query Analyser and did an Index Tune. Turned out that I missed an index on a table. I had SQL server create the index and BINGO! no more problem.
I don't know why this happens.