SAS grid Architecture consideration

[start4mzero]

We have in one of our client's  SAS Grid platform on Linux  having SASWORK and GRIDWORK in the shared storage ( NFS ) . Is this the right approach that SASWORK in shared storage ?
Now we are planning to create a new SAS Grid platform following the above approach of SASWORK in a shared storage ( NFS ) . is this the right approach ? Kindly guide us the right approach .

[LinusH]

Haven't used much.
But a pro for NFS that you might need as much total disk for your work.
But if performance is important, chances are that you probably can get faster disk access with locally mounted disks. To verify, test and/or discus with your infrastructure team.

[start4mzero]

@LinusH Thank you very much for your answer  ! I will check with my infrastructure team 

[JuanS_OCS]

I think this is a tricky question. With NFS you will always hit some important limitation (google it).

Also, NFS has different limitations depending on the version of the protocol, the implementation, and the infrastructure/cloud.

Another reason why makes it tricky.

Normally, for Grid data or Grid SASWORK, I would rather use a proper Distributed Shared  File System, which will face less limitations and risks, on top of higher performance. But, of course, those tend to be expensive solutions for storage.

Do you need SASWORK on shared storage, meaning, will your programs include checkpoints, so your programs can resume from defined points. If you don't I would strongly suggest to run away from the option to put SASWORK/UTILLOC in a shared storage. Local makes more sense.

And if you do need it, and you don't have a DFS available, then try to find your NFS options with your infra team, and try to run enough tests and stress tests, to ensure your Production workloads will go as you expect.