09-22-2017 07:15 AM - edited 09-22-2017 07:18 AM
In traditional SAS/Connect
I need to copy a dataset from a client to a remote server using a remote libname
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
on 09-22-2017 07:40 AM
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.
on 09-22-2017 07:58 AM
According to this, it looks like the PROC SQL only uses multi-threading for group by and order by clauses:
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.
on 09-22-2017 08:20 AM
09-22-2017 08:33 AM - edited 09-25-2017 11:22 AM
Have a nice weekend - looking forward to read about your experience on performance. /Gert
12 hours ago
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.