Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 11339
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Pre modification of job policy based on MMSIM requirements

jehh

Hi,

We have a setup today, where a script running on our LBS (SGE) can suspend jobs on the bulk queue, if licenses are required on a priority queue.

Today, the individual designer has to adjust the requirements field in the job policy such that the required mmsim licenses are known to the script on the SGE.

However, from time to time, a designer might accidentally 'block' many/all licenses on the SGE, due to a mismatch between the requirement field in the jobpolicy and the actual usage.

Is there an 'easy' fix, where the jobpolicy can be automatically adjusted based on the MMSIM requirements?

Or do I need to do a deep dive on some pre-simulation SKILL code that runs a license-check and adjust the job-policy?

BR,

Christian

  •  Hi Christian,

    Since the job is started before the simulation has, it's quite difficult (without a lot of code) to set the job policy dynamically based on the needs of the simulation. Instead, my recommendation would be to instead have APS/Spectre X inherit the resource requirements from the distributed resource management system's resources.

    For example, on the High Performance Simulation options, specify the number of threads as "farm" (or "sge" or "lsf" - but "farm" caters for both) and it will then inherit whatever number of CPUs has been allocated to the job. 

    Otherwise it's a bit of a cart-before-horse problem - you don't know the resources that the simulator needs until it's started. That said, with ADE Assembler the Job Setup form has a "Resources" tab which can be used to try to identify likely resources based on a trial run or on previous simulations. More information  can be found by pressing the Help button on this form.

    Andrew

  • in reply to Andrew Beckett

    Hi Andrew,

    Thank you, this helps a lot! A quick follow up question: Is it possible to setup this up in the .cdsinit?

    BR.

  • in reply to jehh

    You could certainly set the default behaviour for new tests by setting:

    envSetVal("spectre.turboOpts" "numThreads" 'string "farm")

    envSetVal("spectre.turboOpts" "spectreXNumThreads" 'string "farm")

    that won't affect existing tests though. 

    Andrew

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.