[THIN] Re: Web Interface 5.20 slow

  • From: "Foster, Bill" <Bill.Foster@xxxxxxxxxxxx>
  • To: "thin@xxxxxxxxxxxxx" <thin@xxxxxxxxxxxxx>
  • Date: Fri, 2 Oct 2009 09:36:04 -0400

A solution for this is a automated login script. We have one that runs on our 
NetScaler the logs in once a minute and authenticates to the Access Gateway. It 
reduces the wait for users when an iisreset, a reboot  or when the app pool 
does it's restart. It has been remarkably effective for us in greatly reducing 
the occurrence of this issue.

Bill

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of 
Angela Smith
Sent: Friday, October 02, 2009 1:07 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Web Interface 5.20 slow

Hi

Has anyone installed Web Interface 5.2 yet?  I was running Web Interface 5.12 
but was having some slowness issues.  I had already implemented the 
ASPNET.CONFIG updates (generatePublisherEvidence enabled="false") in 5.12 but 
it didn't resolve my issues.  I also turned off "check for server certificate 
revocation" in IE to no avail.

Web Interface 5.2 was only just released.  It already has the ASPNET.CONFIG 
changes in by default but the slowness issues still persist (mainly on first 
access).  Are there any IIS tweaks to ensure all modules are available on 
server startup so the first user does not have slowness issues?

Has anyone rectified this issue in Web Interface V5?

Thanks
________________________________
Let us help with car news, reviews and more Looking for a new car this 
winter?<http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801459%2Fpi%5F1004813%2Fai%5F859641&_t=762955845&_r=tig_OCT07&_m=EXT>
Privacy Notice: This electronic mail message, and any attachments, are 
confidential and are intended for 
the exclusive use of the addressee(s) and may contain information that is 
proprietary and that may be 
Individually Identifiable or Protected Health Information under HIPAA. If you 
are not the intended 
recipient, please immediately contact the sender by telephone, or by email, and 
destroy all copies of this
message. If you are a regular recipient of our electronic mail, please notify 
us promptly if you change 
your email address.

Other related posts: