05-12-2010 04:41 PM
We have an SBS 2003 SP2 which runs our web service for Act! 2010 SP1 as well as a number of other apps, including Outlook Web Access (OWA), a fax server, regular Act! Premium for local users, etc.
When users go to the URL for OWA, the response time for initial screen painting/login is very rapid. When they go to the APFW URL, the response to load the login screen can be over 1 minute. It's like its not in memory NOW, so the server is requesting the service to awaken, and we have to wait to get the login screen. If we were to log off, and then come back to that URL (within say a few minutes), the screen paints rapidly.
In no cases does IE time out awaiting a response - it just waits, and eventually it gets a response. Once we are in APFW (past the login screen), the response time is reasonable.
Any ideas on how to have the APFW respond to initial logins quicker? Is it a matter of having the APFW image in memory?