I tried experimenting reading a plain vanila txt file containing numbers in fixed width format and read in just one variable at the beginning of the record (lrecl=65557) (number of records =1000) using the SAS url engine. The data itself is about 64MB (a slice of a much bigger file) and is stored on a MS ONE DRIVE space with a url to reference the data set with. The ONE DRIVE files also live on the same university net so I don't have to battle the entire Internet to get at the data. It took about 4 wall clock minutes to chew thru the data set but just less than 5 CPU secs, so I know that the hang up is I/O. I don't suspect heavy network traffic to be the culprit but am more inclined to point the finger either at the unknown shims necessary to make ONE DRIVE work or at the SAS url engine. I know that the efficiencies of SAS engines can vary significantly, so I am wondering where the hold up is. If I read the same data set off of a remote PC using 100mps wifi and battling other animals for bandwidth thru CITRIX it takes ~ 2 minutes to read the file. Anyone have any experience with this type of issue? cheers, max
... View more