topic Re: DI THREADS and CPUCOUNT in SAS Data Management

DI THREADS and CPUCOUNT

DavidCaliman — Fri, 05 Dec 2014 16:41:27 GMT

I need any special license to run the SAS to the options below?

-cpucount 4

-threads

I need to increase the processing power in the SAS.

When two jobs perform the same time, the performance is very low.

I added the following command line in the Job and the log did not show anything related to threads.

THREADS=YES CPUCOUNT=4

Re: DI THREADS and CPUCOUNT

Patrick — Fri, 05 Dec 2014 18:34:20 GMT

These options only help you if your process is able to run multithreaded. A SAS datastep for example is single threaded.

But: If two jobs run in parallel impact on each others performance then there must be another problem and it's likely hardware based - eg. a slow disk or network and both jobs are having a lot of I/O.

Re: DI THREADS and CPUCOUNT

jakarman — Fri, 05 Dec 2014 18:58:25 GMT

Reboot your mind and start with evaluating your environments bottom-up and top-down.

At the the top are you performance requirements at the bottom what the hardware can deliver, those worlds should meet each other.
Starting at the bottom review: 42197 - A list of papers useful for troubleshooting system performance problems You will see IO environments are often a bottleneck as of the same for too small size machines (memory).

Thinking on speeding up by faster cpu-s is a hoax, they are not really becoming faster since 2003.

You can run multiple jobs on one machine as long the needed resources (IO - memory) are sufficient. When not there horizontal scaling called grid computing.

There are procedures supporting multithreading as examples sort and proc sql. There are no notes on the log on that. With an excellent system (all cached io) you will see real time (wall clock) becoming less as used time (summing up).

Whether it is legal compliant to do that is just a contract question. Review your contract on that. It could become a loose-loose when you are not able to get this aligned.