Date: Fri, 30 Jul 2004 20:35:32 -0400
Reply-To: Don Henderson <DonaldJHenderson@HOTMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Don Henderson <DonaldJHenderson@HOTMAIL.COM>
Subject: Re: Sloooow SAS/Intrnet
In-Reply-To: <2n04suFrqgjuU1@uni-berlin.de>
Content-Type: text/plain; charset="us-ascii"
Richard's suggestions are definitely things to check. But, permit me to add
a couple points:
1. If your tabulate jobs are connecting to a SHARE server, there might be a
delay due to that. I recall (from a while back) some slowdowns due to SHARE.
2. When you say that the times in the log are the same, do you mean that you
have looked at the SAS LOG for both the IntrNet jobs and a standalone SAS
session? If so, then I would suggest that the difference is due to network
delay as Richard suggests.
3. You refer to startup time for SAS. That would imply you are using either
Launch or Pool services. If Launch, perhaps something has changed to cause
SAS to take longer to come up. Ditto for Pool. However another point to
check for Pool is whether someone changed the minimum number of servers that
are always up and running. If there are fewer servers, you would see the
jobs taking longer when a new App Server needs to be started.
HTH,
-don h.
-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Richard
A. DeVenezia
Sent: Friday, July 30, 2004 7:46 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: Sloooow SAS/Intrnet
Pete Lund wrote:
> I have a strange problem. On one of our development machines I have a
> number of jobs called via SAS\Intrnet that today started running very,
> very slowly.
>
> For example, a TABULATE step takes 8 seconds when the job is spawned
> from a web form. I can run the same job on the same machine against
> the same data in interactive SAS and the step takes .2 seconds.
>
> Two things are curious:
> - these jobs have been around for many, many months and run every
> day and just today they started running slowly
> - the real time difference between interactive and Intrnet is .2 vs
> 8 seconds, but the CPU times (reported in the SAS log) are identical
>
> I don't really even know where to begin looking. I can expect some
> delay while SAS is started up in the background for the Intrnet job,
> but once it's running I'd expect the performance to be about the same.
>
> Nothing else was running on the machine at the time. The real jobs
> that were run have many, many steps and the time discrepancy is
> consistent throughout the job.
>
> Again, this has been working fine for a long time and it's not even
> Friday the 13th. One more tidbit - the production version of this
> application (same code and data on a different machine) still works
> just fine.
>
> I'm running 9.1 on Windows XP Pro.
Did something in the LAN change?
Network printers removed ?
Might the data stores be in contention with something new ? Check your Event
Viewer for anomalies. What mode of Intrnet Service ( Socket/Pool/Launch ) ?
You could add some tracing using Perfmon (type Perfmon in the Run box), or
try some of the utilities at
http://www.sysinternals.com/ntw2k/utilities.shtml. With luck you will find
the bottlenecking culprit.
--
Richard A. DeVenezia
DSGI alternative ? http://www.devenezia.com/downloads/sas/samples#jDSGI
