SAS Studio 3.8 slow to start on Windows 10

[itbminer]

Hi all,

I'm using SAS Studio 3.8 on Windows 10 on my laptop and have noticed it's quite slow till I get to SAS Studion Single User screen in my browser. When I say slow it takes over a minute before I'm able to access the UI. It takes most time while the progress spinner is saying "signing in".  I have launched SAS Studio on an AWS instance and it's been much much faster as when once the instance is started on AWS I can access the UI in around 10 seconds.

Is there anything that could be causing this to slow down?

The following is information on my system:

Release: 3.8 (Single User)

Supported browsers:

• Microsoft Internet Explorer 11
• Mozilla Firefox 21+
• Google Chrome 27+
• Apple Safari 6.0+ (on Apple OS X)

Build date: 6 Nov 2018 20:57:53
SAS Mid-tier release: 6 Nov 2018 20:55:00
Java Version: 1.7.0_76
SAS release: 9.04.01M3P06242015
SAS platform: X64_8PRO WIN

Thanks

[CaseySmith]

Hi @itbminer,

The time it takes to launch the Single User edition of SAS Studio can definitely take longer than connecting to the Basic or Enterprise editions of SAS Studio.  Unlike the Basic and Enterprise editions, the Single User edition of SAS Studio requires a local controller to run.  For example, in your Windows tray (after launching SAS Studio once), you should see a server icon labelled "SAS Studio 3.8 Controller (http://localhost:nnnnn/)" (which corresponds to the SASStudioHost.exe process).  This controller has to start-up before SAS Studio can start, so the first launch of (single user edition) SAS Studio almost always takes longer than subsequent launches of SAS Studio.

For me, the Single User Edition of SAS Studio 3.8 takes around 45 seconds to start "cold" (when it has to start the controller) and around 20 seconds to start "warm" (when the controller is already running -- subsequent launches of SAS Studio).

Do you see the >1 min delay every time you start SAS Studio, or mainly the first time after you logon or restart Windows?  If the first time is the primary issue, you could consider starting SAS Studio 3.8 ("C:\Program Files\SAS\SASStudioSingleUser\3.8\SASStudioHost.exe") at Windows Startup, so that it goes ahead and starts the controller.  Then when you are ready to use SAS Studio, subsequent launches will be faster (since the controller will have already been started).

Casey

[itbminer]

Hi @CaseySmith,

Thanks for your reply, I hadn't noticed the controller in the system tray. Yes it's similar to what you have described once the controller is started it's faster to launch than starting "cold" but not that much more for me a t least. Its still taking about 40 to 50 seconds before I can access the UI in a browser.

It's nearly quicker as quick to use the VM with the SAS Studio University edition.