[THIN] Re: FYI Smartstart and app launch times

  • From: "Lilley, Brian" <brian.lilley@xxxxxxxx>
  • To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
  • Date: Wed, 15 Sep 2004 10:17:51 +0100

Ron, Are you able to supply detail of what point autoexec is called?  Also,
are you able to confirm if autoexec.bat needs to be in the root.
 
Thanks, Brianos

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of
Ron Oglesby
Sent: 15 September 2004 02:27
To: thin@xxxxxxxxxxxxx
Subject: [THIN] FYI Smartstart and app launch times



OK, Myself and another participant on the list (jeff Matheis) have figured out
something interesting.

 

At his location and another client they were experiencing some "slow" launch
times. Slow being relative and being between 18 seconds and 30 with an
explicit app and on the first connection. In both locations the Servers were
HP servers built with Smart start (or at least smartstart then imaged). Anyway
in both sites we ran a winlogon debug and noted the same thing, a 9-12 second
delay in the logon process where Autoexec.bat was attempting to be processed.

 

In both cases the smartstart builds left the autoexec.bat off the system (not
like you need it right) anyway, by placing an empty autoexec.bat out there for
processing we dropped about 10 seconds off of the app launch time. In my
recent client this got our anonymous apps down to 4-5 seconds and our domain
explicit logins down to 7 - 9. 

 

Just an FYI for the list. Another of those untold number of little things we
have to do to make it "right"

 

Ron Oglesby

Senior Technical Architect

Microsoft MVP - Windows Server Technologies

 

RapidApp, Chicago

Mobile: 815 325 7618

 


==============================================================================
This message is for the sole use of the intended recipient. If you received
this message in error please delete it and notify us. If this message was
misdirected, CSFB does not waive any confidentiality or privilege. CSFB
retains and monitors electronic communications sent through its network.
Instructions transmitted over this system are not binding on CSFB until they
are confirmed by us. Message transmission is not guaranteed to be secure.
==============================================================================

Other related posts: