Thank you for useful command to see the node labels and suggestion to keep all the workload for compute server in one place! We will consider to try it out in our cluster. Looking forward to next blogs about how many compute nodes do you need or finding answer to questions like: do you need another stateless node or another compute node if there is significant programming workload, however based on past experience there is also a need for stateless/stateful node with more CPU than for compute node. One thing I was missing in the blog is, where can you find the default deployment for stateful/stateless nodes except of site.yaml , with the nodes affinity and tolerations requirements? ... View more

Hi @touwen_k ,   Thanks for you comment and question. It's good to hear you are beginning to use SAS Workload Orchestrator (SWO). When you ask "If adding more compute nodes, for example for SAS Studio, is it correct that you need more cores than memory?" I'm not quite sure what is being asked. Typically we see nodes being used that have 8 cores with 64GB of RAM or 16 cores with 128GB of RAM. But there are smaller nodes with say 4 cores with 16GB of RAM that some customers may find perfectily acceptable for their use cases.   There are ways to set the maximum number of jobs per vCPU and depending on the types of workloads and their priorities, the use of WLM can certainly help manage Compute workloads. And of course the use of queues and how they can be aligned with different node pools.   I think you may find these papers useful:   https://communities.sas.com/t5/SAS-Communities-Library/An-Autoscaling-Experience-on-SAS-Viya/ta-p/895678 https://communities.sas.com/t5/SAS-Communities-Library/Scaling-to-new-heights-Exploring-the-auto-scaling-capabilities/ta-p/886389 https://communities.sas.com/t5/SAS-Communities-Library/Azure-Spot-Instances-for-SAS-Workload-Management/ta-p/918810   Cheers, Simon   ... View more

Well explained concepts, it makes clear why one needs to implement the taints. I love the scenarios, they make it easy to follow blog ... View more

I liked the part about cleaning midtier and cache. It was very clear explained. Do you need to do that in M8 as well? ... View more

hello @Wilbram-SAS , I have followed your workshop and have successfully established connection with Viya 4. I am now able to see the SAS 9.4 folders from Viya in the left panel of EG and also my mounted path in Viya. However when assigning caslibs they are not visible in the left panel. Is this correct or am I missing something? regards Karolina T ... View more

@NicolasRobert  hello Nicolas, thank you for checking. We have just updated to version 2024.04. Our users have put the libraries in different tab Resources, and then you cannot start the compute session.   ... View more

@thesasuser  - Reviewing the SAS Viya System Requirements for resources including storage would be a good starting point: https://documentation.sas.com/doc/en/itopscdc/v_052/itopssr/n0ampbltwqgkjkn1j3qogztsbbu0.htm ... View more

Hi you're correct in your reasoning.   I checked the documentation and pasted the confirmation here: The preempted job is requeued in order to run again if the following criteria are met: The job that was preempted and killed is identified as being restartable. The queue on which the job was running is also configured as being restartable. The only jobs that can be restarted are jobs that are submitted using the  sas-viya batch jobs submit-pgm  command and one of the following input options: --restart-datastep --restart-label --restart-job See Submit SAS Programs in Batch in Using the batch Plug-In for the SAS Viya Platform Command-Line Interface for information about these options. By assigning one group of hosts for high-priority jobs and a different group for medium- and low-priority jobs, you can ensure that low-priority jobs are not held, waiting for higher-priority jobs to complete processing. Or like you suggested you can experiment with the Job Execution Time-out like described here.   ... View more

The option with shortcuts is great! ... View more

@EdoardoRiva As we do not have experience yet with SAS Workload Orchestrator, we would like to know what the best practice is. We are not going to use preemption yet as you have to find out how to program jobs to restart. So if we schedule priority jobs and the other less important jobs fail because they are too long in a pending state, what is best practice if you want these less important jobs to run as well? Is extending the default time-out of compute session the best practice or are there another solutions? Is it possible to advise as we are eager to use these feature very soon. ... View more

@GillesChrzaszcz   As we do not have experience yet with SAs Workload Orchestrator, we would like to know what the best practice is. We are not going to use preemption yet as you have to find out how to program jobs to restart. So if we schedule priority jobs and the other less important jobs fail because they are too long in a pending state, what is best practice if you want these less important jobs to run as well? Is extending the default time-out of compute session the best practice of are there another solutions? Pls advise as we are eager to use these feature.   ... View more

srinivas.007@yahoo.com   sgundala@svb.com   These are my e-mail ids to share the Workshop Materials.     Thanks in advance. ... View more

Does anyone have updated instructions to work on the latest SAS Viya 2024.02 ? ... View more

Very good blog @HansEdert  Will use it as a reference. ... View more

Thank you very much for your answer! ... View more