Starting with SAS 8 released in 1999, Multi-Process Connect ( MP CONNECT) parallel processing functionality was added to SAS/CONNECT enabling you to execute multiple SAS sessions asynchronously. That was client/server, but not parallel processing. That is when a remote session was started, the client session was suspended until processing by the server session had completed.
In its original incarnation SAS/CONNECT allowed only synchronous execution of the SAS remote sessions. SAS/CONNECT® is one of the oldest SAS products that was developed to enable SAS programs to run in multi-machine client/server environments. You might be surprised at how easily this can be done, and at the same time how powerful it is. The same principle of parallel processing (or parallel computing) is applicable to SAS programs (or non-SAS programs) by running their different independent pieces in separate SAS sessions at the same time (in parallel). That’s the power of running water in parallel. They clearly and convincingly demonstrate that two pipes will fill up a swimming pool faster than one.
I am sure you remember those “filling up a swimming pool” math problems from elementary school. Think about it: if you have two SAS programs one of which runs 3 hours, and the second one runs 2 hours, their total duration will be 5 hours if you run them one after another sequentially, but it will take only 3 hours if you run them simultaneously, in parallel. While it is customary to think that 3+2=5, it is only true in sequential world. As earth completes its routine annual circle around the sun and a new (and hopefully better) year kicks in, it is a perfect occasion to reflect on the idiosyncrasy of time.
0 kommentar(er)
