As a thought. CFSERVER on win2k isn't run as an ISAPI filter afaik. Its called as a DLL, but process execution opperates under the Cold Fusion processes. As aprt of debugging site instances, we fairly regularly have to attempt to track the source of server resource consumption on a shared server. I can say with a fairly monsterous ammount of confidance that on win2k with cf4.0/5.0/MX DLLHOST processes are typically not associated with Cold Fusion consumption. With CFMX the Jrun.exe, and in CF5.0 CFSERVER.EXE will normally be the process with resources consumed in relation to CF code and cfexec will be running, but typically not consuming many resources. This is a pain in the arse cause you can quite easily associate a dllhost with specific site instance (set hight/isolated, match the process ID for the memory consuming dllhost with the process ID listed next to slots in component services and play join the dots.)
If you're running CF as an ISAPI filter through some stretch I'm not aware of? I'd probably reccomend against it given how ISAPI filters behave. Just a default install tiein with CF and win2k thought will not be running through the DLLHOSTS. Just in the name of scientific experimentation, since I realised I hadn't actively gone looking on CFMX as yet, I've just fired a perpetual loop across my dev box just dumping CGI and calling the same page again. Jrun pushes to about 60% cpu usage and a higher then usual ram consumption, DLLHOST's don't bat an eyelid. I'd suspect if your DLLHOSTS are consuming ASP resources out of hand, you probably need to check into your ASP applications rather then CF. -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Friday, 21 March 2003 3:38 AM To: CF-Talk Subject: RE: DLLHOST.exe woes. Part of ColdFusion MX? IIS Connector? > Hey there again > > I'm wondering what part DLLHOST.exe plays in the coldfusionMX > implementation. > > It would make sense that dllhost.exe is what is calling the > coldfusion connector... right? > > Is it normal for DLLHOST to be using more processing power > then the jrun.exe process? > > Does DLLHOST play an intricate part in the page assembly? When you use CF (MX or any other version) with IIS, within IIS you have an "Application Isolation" option for each virtual server. If you choose "Low", the CF ISAPI DLL will be run in-process by the IIS process (INETINFO.EXE, I think). If you choose "Medium" (in IIS 5) or "High", the CF ISAPI DLL will be run out-of-process. Since it's a DLL, not an EXE, it has to be run by something else, and that something else will be DLLHOST.EXE in this case. So, if you have "Application Isolation" set to "Medium" or "High" for the virtual servers running CF, it's not unusual to see high memory usage by DLLHOST.EXE. Macromedia recommends that you run the CF ISAPI DLL in-process for better performance, in which case you wouldn't see DLLHOST.EXE using the memory, but rather INETINFO.EXE. There's nothing necessarily wrong with seeing high memory usage by either, though, as long as your server remains responsive. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
