Hi folks!
In traditional SAS/Connect
I need to copy a dataset from a client to a remote server using a remote libname
So far:
data remote.mydata;
set local.mydata;
run;
is slow, so is Proc SQL
Ihe datastep only runs on one core (out of 40 available) - right? But PROC SQL should be able to run on eg 4 cores. But the elapse time in the saslog is almost the same. THREADS is enabled and CPUCOUNT=4 in config.
Why is SQL not faster than Data?
Bandwith is about 10Gb/s
Any ideas?
Hrmm...
according to the manual it
"Restores a transport file created by the CPORT procedure."
My data is not a transportfile, but a plain SAS dataset.
Hi
According to this, it looks like the PROC SQL only uses multi-threading for group by and order by clauses:
http://support.sas.com/rnd/scalability/procs/index.html
Another issue could be the bandwidth not being 10Gb/s all the way between the two servers, but as the cpu time in the log is significant compared to real time in both cases, I guess it has to do with single-threading.
Not sure how to overcome the issue apart from hardcode the input into chunks, and transfer them seperately in parallel.
Christian
Have you tried proc upload?
No - I suppose it also runs single threaded. But I will try - just in case 🙂
Have a nice weekend - looking forward to read about your experience on performance. /Gert
We'll wrap this question up at out SASNineNetwork meeting at Thursday in Copenhagen. I have some conclusions - but not all the way around the topic.
SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!