Fluorine very slow under IIS7

I just upgraded my workstation from Windows XP Pro 32 bit to Windows 7 Pro 64 bit. I can get my Fluorine web applications to work fine in both the Classic .NET app pool and the Default app pool (integrated). The problem is that remoting calls are very slow regardless of how I configure the web app. Doing a very simple call to a method that strictly returns a Boolean takes about 2 full seconds to complete. If I debug the web app (using IIS7 and not the ASP.NET development server) and put a breakpoint at the return statement in the method it takes about half a second for that point to get hit after invoking the method and then about 1 – 1.5 seconds for the return value to get back to the Flex 3 application. If I copy the Fluorine app to another machine running Windows Server 2003 and IIS6 and invoke the same method it returns instantly.

Any ideas what to look for to speed things up? Thanks!

Make sure the machine isn't bogged with unneeded services (esp check searchindexer.exe) and use ProcExp64 to figure this out (the old link was www.sysinternals.com).  That's the first thing I'd check, maybe you did and everything else runs fine and the CPU is near idle normally??  I just did an upgrade from Vista 64 to Win7 64 and it basically didn't work, the machine ran like sht...  This is an 8 core 8GB dual opteron workstation and I had performance issues too.  I'd do a thorough and deep eval of the system...  Maybe some guys on the list though know of specific issues running fluorine on 64bit boxes, I haven't seen any.

I just upgraded my workstation from Windows XP Pro 32 bit to Windows 7 Pro 64 bit. I can get my Fluorine web applications to work fine in both the Classic .NET app pool and the Default app pool (integrated). The problem is that remoting calls are very slow regardless of how I configure the web app. Doing a very simple call to a method that strictly returns a Boolean takes about 2 full seconds to complete. If I debug the web app (using IIS7 and not the ASP.NET development server) and put a breakpoint at the return statement in the method it takes about half a second for that point to get hit after invoking the method and then about 1 – 1.5 seconds for the return value to get back to the Flex 3 application. If I copy the Fluorine app to another machine running Windows Server 2003 and IIS6 and invoke the same method it returns instantly.

Any ideas what to look for to speed things up? Thanks!

Thanks for the tips, but everything is running great aside from this. Using a regular .NET web application with forms and database calls is just as fast as it was on XP. I’m also running a new Intel SSD so indexing is already done and disk access is lightning fast. CPU usage is very low while the remoting call is running slowly so there is no antivirus overhead or anything else causing spikes. I would imagine this is just something that needs to be tweaked with IIS since it has changed so much and there are a lot of new settings that I’ve never seen before.

Make sure the machine isn't bogged with unneeded services (esp check searchindexer.exe) and use ProcExp64 to figure this out (the old link was www.sysinternals.com).  That's the first thing I'd check, maybe you did and everything else runs fine and the CPU is near idle normally??  I just did an upgrade from Vista 64 to Win7 64 and it basically didn't work, the machine ran like sht...  This is an 8 core 8GB dual opteron workstation and I had performance issues too.  I'd do a thorough and deep eval of the system...  Maybe some guys on the list though know of specific issues running fluorine on 64bit boxes, I haven't seen any.

I just upgraded my workstation from Windows XP Pro 32 bit to Windows 7 Pro 64 bit. I can get my Fluorine web applications to work fine in both the Classic .NET app pool and the Default app pool (integrated). The problem is that remoting calls are very slow regardless of how I configure the web app. Doing a very simple call to a method that strictly returns a Boolean takes about 2 full seconds to complete. If I debug the web app (using IIS7 and not the ASP.NET development server) and put a breakpoint at the return statement in the method it takes about half a second for that point to get hit after invoking the method and then about 1 – 1.5 seconds for the return value to get back to the Flex 3 application. If I copy the Fluorine app to another machine running Windows Server 2003 and IIS6 and invoke the same method it returns instantly.

Any ideas what to look for to speed things up? Thanks!

Update: Although my test application only was returning a Boolean I forgot that the application was also configured to use an ILoginCommand authentication mechanism which was getting invoked during my test method. Without this the calls are instant which leads me to believe it’s a database access problem since my DoAuthentication call hits the database each time. I’ll post once more when I figure out the issue so hopefully those of you that upgrade to IIS7 can know to look for this.

Thanks for the tips, but everything is running great aside from this. Using a regular .NET web application with forms and database calls is just as fast as it was on XP. I’m also running a new Intel SSD so indexing is already done and disk access is lightning fast. CPU usage is very low while the remoting call is running slowly so there is no antivirus overhead or anything else causing spikes. I would imagine this is just something that needs to be tweaked with IIS since it has changed so much and there are a lot of new settings that I’ve never seen before.

Make sure the machine isn't bogged with unneeded services (esp check searchindexer.exe) and use ProcExp64 to figure this out (the old link was www.sysinternals.com).  That's the first thing I'd check, maybe you did and everything else runs fine and the CPU is near idle normally??  I just did an upgrade from Vista 64 to Win7 64 and it basically didn't work, the machine ran like sht...  This is an 8 core 8GB dual opteron workstation and I had performance issues too.  I'd do a thorough and deep eval of the system...  Maybe some guys on the list though know of specific issues running fluorine on 64bit boxes, I haven't seen any.

I just upgraded my workstation from Windows XP Pro 32 bit to Windows 7 Pro 64 bit. I can get my Fluorine web applications to work fine in both the Classic .NET app pool and the Default app pool (integrated). The problem is that remoting calls are very slow regardless of how I configure the web app. Doing a very simple call to a method that strictly returns a Boolean takes about 2 full seconds to complete. If I debug the web app (using IIS7 and not the ASP.NET development server) and put a breakpoint at the return statement in the method it takes about half a second for that point to get hit after invoking the method and then about 1 – 1.5 seconds for the return value to get back to the Flex 3 application. If I copy the Fluorine app to another machine running Windows Server 2003 and IIS6 and invoke the same method it returns instantly.

Any ideas what to look for to speed things up? Thanks!

The culprit turned out to be a combination of NOD32 antivirus (specifically the HTTP scanning) and the ASP.NET state service. I could’ve sworn I tried disabling NOD32 before but maybe not fully. So it had nothing to do with Fluorine but hopefully in case any of you upgrade soon and are running the same combination of software this can save you a few hours of headache.

Update: Although my test application only was returning a Boolean I forgot that the application was also configured to use an ILoginCommand authentication mechanism which was getting invoked during my test method. Without this the calls are instant which leads me to believe it’s a database access problem since my DoAuthentication call hits the database each time. I’ll post once more when I figure out the issue so hopefully those of you that upgrade to IIS7 can know to look for this.

Thanks for the tips, but everything is running great aside from this. Using a regular .NET web application with forms and database calls is just as fast as it was on XP. I’m also running a new Intel SSD so indexing is already done and disk access is lightning fast. CPU usage is very low while the remoting call is running slowly so there is no antivirus overhead or anything else causing spikes. I would imagine this is just something that needs to be tweaked with IIS since it has changed so much and there are a lot of new settings that I’ve never seen before.

Make sure the machine isn't bogged with unneeded services (esp check searchindexer.exe) and use ProcExp64 to figure this out (the old link was www.sysinternals.com).  That's the first thing I'd check, maybe you did and everything else runs fine and the CPU is near idle normally??  I just did an upgrade from Vista 64 to Win7 64 and it basically didn't work, the machine ran like sht...  This is an 8 core 8GB dual opteron workstation and I had performance issues too.  I'd do a thorough and deep eval of the system...  Maybe some guys on the list though know of specific issues running fluorine on 64bit boxes, I haven't seen any.

I just upgraded my workstation from Windows XP Pro 32 bit to Windows 7 Pro 64 bit. I can get my Fluorine web applications to work fine in both the Classic .NET app pool and the Default app pool (integrated). The problem is that remoting calls are very slow regardless of how I configure the web app. Doing a very simple call to a method that strictly returns a Boolean takes about 2 full seconds to complete. If I debug the web app (using IIS7 and not the ASP.NET development server) and put a breakpoint at the return statement in the method it takes about half a second for that point to get hit after invoking the method and then about 1 – 1.5 seconds for the return value to get back to the Flex 3 application. If I copy the Fluorine app to another machine running Windows Server 2003 and IIS6 and invoke the same method it returns instantly.

Any ideas what to look for to speed things up? Thanks!