Greetings, Just thought I'd let everybody know that we were able to resolve our performance issue. It turns out we had our Service Network switches set to Auto Negotiate.
We changed them over to 100 full and execution times went back to normal. Thanks for all the suggestions. JD. -----Original Message----- From: Reuter, Jason D (James Tower) [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 1:23 PM To: CF-Server Subject: RE: Application Execution Time issues on Remote Share Thanks for the quick responses. We actually did try just a straight IP to the remote machine and it didn't really change the unusually high "STARTUP, PARSING, & SHUTDOWN" execution time. We did have a support call to our CF representative. One of his suggestions was to not store the CF code on a remote server (??), which kind of defeats the purpose of trying to separate file storage from the application/web server. Someone mentioned turning DNS caching on, but I don't believe this option is a service in IIS 4.0 (not 100% sure). If anyone else has any other ideas, or knows why separating cfm files onto a resource server is not an optimal architecture, please feel free to comment. Thanks, JD -----Original Message----- From: Steve [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 10:40 AM To: CF-Server Subject: Re: Application Execution Time issues on Remote Share Try using a host file or call the remote machine via IP addr. See if that speeds it up. Steve ----- Original Message ----- From: "Reuter, Jason D (James Tower)" <[EMAIL PROTECTED]> To: "CF-Server" <[EMAIL PROTECTED]> Sent: Thursday, May 16, 2002 9:06 AM Subject: Application Execution Time issues on Remote Share > Greetings, > > Having a rather bizarre problem I'm hoping someone can shed some light on. > > We are noticing some strange behavior from Cold Fusion while attempting to > employ a remote "resource" server architecture. > > Basically, the head end web servers (WF40P1 & WF40P2) run IIS 4.0 and CF > 4.5.1 SP2 and no code locally. The home directory for the site is mounted > from a standard Windows File Share on the Resource Server (WF40R1). This is > where all Cold Fusion code resides. > > The site functions normally, but what we noticed at first was incredibly > slow application execution time compared to our stand alone servers. We > predicted a small possibly degradation, but not 10 times slower. > > After further review, and with full debugging on, we have seen the > following: > > Application executes normally with all code local (Approx. 400ms) > When accessing the remote code base from the Resource server using the UNC, > we get up to 10 times slower execution time. > If we force IIS to map the Virtual directory to a statically mapped network > drive, we return to normal execution times. > > So, in summary: > Local Code: normal > Remote Code via UNC Share: Very Slow > Remote Code via Mapped Network Drive: Normal > > I was hoping someone may have some insight on why this is occurring, and can > better explain what Cold Fusion is doing behind the scenes. My initial > thoughts were that CF attempts to authenticate against the NT domain for > each resource (page) it is trying to access, or it is repeatedly doing a > name lookup of the resource server for each page it is retrieving. > > Thank You, > -JD > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com ------------------------------------------------------------------------------ To unsubscribe, send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
