topic Re: E-Minor Slowness in Administration and Deployment

SAS Enterprise Miner Slowness

ardobbins — Wed, 24 Aug 2016 20:27:52 GMT

Hello,

I"m new to the SAS Platform. I've recently been brought on to be a Platform Administrator. I've been tasked with troubleshooting 2 problems with our SAS deployment as of right now.

One is, our E-Miner platform has been running slow, giving us green check marks as everything is ok, rejecting data, and not giving any output.

Our other problem is, when running scheduled jobs overnight in EG, some the same jobs processing the same data has started to run 2-3 hours longer.

What are some steps I can take to start resolving these issues?

Thanks!

Re: E-Minor Slowness

MargaretC — Wed, 24 Aug 2016 19:09:00 GMT

Can you share with us SAS logs from either example? Preferrably with the following SAS statements added to the start of the SAS process?
OPTIONS FULLSTIMER SOURCE SOURCE2 MSGLEVEL=I MPRINT NOTES;
PROC OPTIONS GROUP=MEMORY;
PROC OPTIONS GROUP=PERFORMANCE;
RUN;
LIBNAME _ALL_ LIST;
PROC OPTIONS OPTION=WORK;
PROC OPTIONS OPTION=UTILLOC;
RUN;
DATA _NULL_;
%PUT This job started on &sysdate at &systime;
RUN;

Re: E-Minor Slowness

ardobbins — Wed, 24 Aug 2016 19:43:44 GMT

Attaching to the job in E-Minor and should have something today.

Attaching to one of the jobs that runs over night so we will have it in the logs the next time it runs slow.

Re: E-Minor Slowness

ardobbins — Wed, 24 Aug 2016 19:46:33 GMT

Attached is from the E-Minor Job.

Thank You!

Re: E-Minor Slowness

MargaretC — Wed, 24 Aug 2016 19:52:05 GMT

Thank you for the short SAS log that gives me the output from thestatements I had you add to the EM project.

There are lots of LIBNAME statements to Oracle. Are the steps that are running slow (which are not included in the SAS log you sent) accessing any of these libraries? If so, your slowness may be coming from extracting data from Oracle.

Again, a SAS log showing the steps that are running slower is needed.

Cheers,

Margaret

Re: E-Minor Slowness

ardobbins — Wed, 24 Aug 2016 20:00:30 GMT

LOL - My apologies. I didn't preview the attached. I'm having the user run a big job and send over the logs tomorrow and I will attach again.

Thank You!

Re: E-Minor Slowness

Reeza — Wed, 24 Aug 2016 20:30:00 GMT

You're also running a lot over networks, check your network performance.

Re: E-Minor Slowness

ardobbins — Thu, 25 Aug 2016 13:18:17 GMT

Attached is the log file from E-Miner.

Re: E-Minor Slowness

Reeza — Thu, 25 Aug 2016 13:28:05 GMT

There didn't seem to be anything in the code related to EM, albeit it's long and I may have missed something.

If you're running this on EM maybe you can move it to a full SAS installation to see if it's faster.

Re: E-Minor Slowness

ardobbins — Thu, 25 Aug 2016 13:50:25 GMT

More information on the problem --- All the boxes on the modules get green check marks as the program ran correctly but there are no results are generated. Would screen shots help?

Re: E-Minor Slowness

Reeza — Thu, 25 Aug 2016 14:01:47 GMT

The results are tables. The final table should be in the tt library. La_all I think.

Does it exist?

Re: E-Minor Slowness

ardobbins — Thu, 25 Aug 2016 14:33:18 GMT

Yes, that table does exist. There are several intermediate tables created during the process. No other outputs. The final result was the creation of that tt.la_alll table.

Re: E-Minor Slowness

ardobbins — Thu, 25 Aug 2016 14:47:55 GMT

Attahced are screenshots of what all our EMINER outputs are looking like.

Re: E-Minor Slowness

MargaretC — Thu, 25 Aug 2016 15:07:49 GMT

There seems to be some IO performance issues with two different directories that you are using. SAS WORK which is pointing to e;\WORK and TT which is pointing to \\aacadasas\cada. Can you give me more details on what type of storage each of these file systems are pointing to?

Also, why do you have MEMSIZE equal to 75GB? That is really high.

Cheers,

Margaret

Re: E-Minor Slowness

ardobbins — Thu, 25 Aug 2016 16:37:56 GMT

SAS WORK and aacadasas/dada are on the same drive just a different path.

I'm not sure about MEMSIZE. Is that set per program or is it a default in the SAS config? What would you recommend it being set to?

Re: E-Minor Slowness

anja — Thu, 25 Aug 2016 16:47:17 GMT

Hi,

have you contacted Tech Sup yet? If not, that might be something to run by TS. https://support.sas.com/techsup/contact/

Thanks

Anja

Re: E-Minor Slowness

MargaretC — Thu, 25 Aug 2016 16:51:21 GMT

Can you explain to me what you mean by disk? Is this a single hard drive in your computer? If so, we have figured out your problem. A single hard disk drive can not give you the IO performance needed for SAS.

Again, can you give us more specifics on the disks used to create the E:\ file system.

Re: E-Minor Slowness

ardobbins — Thu, 25 Aug 2016 16:56:03 GMT

Our E drive is a total of 14 disk using Raid-10. The E Drive is used to write our data sets to and is also used as our work directory.

Re: E-Minor Slowness

MargaretC — Tue, 30 Aug 2016 18:55:32 GMT

I got pulled into another project the end of last week. How many concurrent SAS jobs are running at any given time on your system? 7 drives may not be enough to give you the 100 MB/sec/physical core in your system that the SAS WORK file system needs.

Re: E-Minor Slowness

ardobbins — Tue, 30 Aug 2016 19:10:17 GMT

Hello Margret,

I'm not sure how many jobs during the day may be going at one time. We currently have about 60 workspaces spawned at the moment. We run right at 100 jobs from 12:30am - 9am.

I do have a decent background on the hardware side of servers. I do believe the bottleneck in our system is the I/O. Is there someone I can consult with through messaging, email, phone, in effort to increase our I/O capabilities?

Do you think that the WorkSpace disk should be shared where the datasets are or should it have it's own disks?

We have a SAN drive we can implement from our old SAS deployment. What could we use it for to get the best benefit?

Thanks for any advice.