@Quentin wrote:
Did you try @SASKiwi 's suggestion?
Yeah. No luck.
I know EG added the "project-less" option in 8.1 (https://go.documentation.sas.com/doc/en/egug/8.3/p10qv233h1du0un1vzhdxw320vqg.htm) but I've never really understood why people wouldn't want to use a project. I only use projects as as a collection of links, but it's still handy.
We are all very new to EG, so the concept of project feels foreign and scary to us. And mostly unnecessary, since we very often just run individual programs anyway.
Are you saying your users use EG without a project, open a program, run it, and EG still returns a bunch of output tables and adds them to a process flow or some-such?
Yes, but I don't think it adds anything to a process flow or anything. I don't even really know what that is. It operates more or less like desktop SAS, except desktop SAS doesn't have an Output Data tab.
Depending on network speed, EG can feel slow, especially when it has to return a big log file, big output file, etc. Many companies find it faster to set up a terminal server that is near the SAS server, with EG running on the terminal server. Then users can remote into the terminal server and run EG sessions there. So you drastically reduce the distance between the EG client and the SAS server.
Yeah, that's kind of the problem. Our terminal servers were originally all located in US West, but our East Coast users were experiencing latency in general, so we added terminal servers closer to them, but now when running a program in EG, there seems to be additional fixed slowness at the beginning (not an issue) and a variable slowness after the log shows that the program is done running, and this slowness seems to scale with the number of output datasets. My inference is that the slowness is caused by SAS having to download all the datasets in the "output data" tab, but I don't have a way to test that since I don't seem to be able to turn off the ability to download those datasets.
... View more
