In a recent blog post, we announced the availability of Univa Unisight 4.3. And although you might not anticipate much in just a ‘dot’ release, that was simply not the case. In fact the Rules Engine capability, brand new to this version 4.3 release, is proving to be quite a significant enhancement.
Regarding the Rules Engine, in that same blog post we stated: “The [Rules Engine] is rich and robust enough that it is already being used to automate preemptive scheduling capabilities – a natural augmentation of the manual preemption capability we introduced in version 8.3 of Univa Grid Engine some time ago …” Since our recent webinar actually provides a demonstration of an automated use case for preemptive scheduling, we thought we might mention that here as well, and provide a little more context.
Automating preemptive scheduling with Univa Unisight 4.3 is not only a BIG DEAL for our enterprise customers, it’s actually a BIG DEAL for HPC. Whereas many pay lip service to preemptive scheduling, few implement it fully – and this includes, e.g., queue subordination in open-source Grid Engine. So, when manual preemption was first introduced over two years ago into version 8.3.0 of Univa Grid Engine, it truly was a BIG DEAL as related by our Vice President of Products and Services Bill Bryce. In this still-relevant article that appeared in insideHPC, Bill provides ample context for the value of this feature to our enterprise customers.
Of course, no good deed goes unpunished. And as you might anticipate, as soon as our savvy customers gained comfort with manual preemption in Univa Grid Engine, they wanted MORE – where more equated to their need to enable automated strategies for preemption. With the Rules Engine capability now a core component of Univa Unisight, these same customers can revisit their preemption use cases and introduce automation where appropriate.
While automating use cases for preemptive scheduling via the Rules Engine capability provided by Univa Unisight can certainly seem appealing, we still recommend sparing use of the same. Why? Briefly, manual or automated, preemptive scheduling is a highly invasive scheduling policy. And if you find yourself gravitating towards a constant need for preemption, chances are there are other, more-appropriate scheduling policies that might serve your organization’s overarching objectives more effectively – e.g., an entitlement-based policy designed around projects and limited with quotas.
We love to discuss your scenarios for workload management, and making those scenarios highly visible to you. The combination of Univa Grid Engine and Univa Unisight is a particularly compelling combination in this regard. Whether it’s automated preemption, or some other set of requirements, we look forward to that discussion – in person at SC17 perhaps, or via the usual channels.