• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Adexl - max jobs not exceeding limit 100

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 3765
  • 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

Adexl - max jobs not exceeding limit 100

firebolt
firebolt over 2 years ago

I saved a job policy with max jobs 1000 and defined same in cdsinit. When simulation is fired and I check individual test job setup, it gets reverted to 100 but no change in command. I verified in bjobs list. I see 100 running jobs only and nothing in pending. And in adexl interactive, I see rest 50 in pending state because they are not submitted to farm yet by adexl (I think). Confirmed with local CAD guy, no limit on number of spectre/bjob licenses (probably not 100). Please help here. 

envSetVal("adexl.icrpStartup" "defaultJobPolicy" 'string "bsub44")

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    A few points:

    1. You should be using ADE Assembler rather than the obsolete ADE XL
    2. ADE remembers the last job policy used in that ADE XL/maestro view and that's what will be shown next time, even if you change the default (the default is for new views).
    3. You appear to be using the per-test job policy settings (Right Mouse over the test name in the Data View assistant, then pick Job Setup). You only really should use that if you really need to override it per-test, otherwise you'd use the setting for all tests using the Options->Job Setup menu in ADE. Again, the per-test job setup will be retained if set
    4. 1000 jobs is likely to strain the ADE infrastructure with ICRP; you should switch to ADE Assembler and use LSCS if you want to run this number of jobs in parallel.

    Andrew

    • Cancel
    • Vote Up +2 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    A few points:

    1. You should be using ADE Assembler rather than the obsolete ADE XL
    2. ADE remembers the last job policy used in that ADE XL/maestro view and that's what will be shown next time, even if you change the default (the default is for new views).
    3. You appear to be using the per-test job policy settings (Right Mouse over the test name in the Data View assistant, then pick Job Setup). You only really should use that if you really need to override it per-test, otherwise you'd use the setting for all tests using the Options->Job Setup menu in ADE. Again, the per-test job setup will be retained if set
    4. 1000 jobs is likely to strain the ADE infrastructure with ICRP; you should switch to ADE Assembler and use LSCS if you want to run this number of jobs in parallel.

    Andrew

    • Cancel
    • Vote Up +2 Vote Down
    • Cancel
Children
  • firebolt
    firebolt over 2 years ago in reply to Andrew Beckett

    Yes, I am using Maestro only. Even with global job setup, say max jobs 300, still I see jobs limited to 100. Let me check with LSCS. What's the difference between LSCS & ICRP?

    envSetVal("maestro.lscs" "defaultSimulationJobPolicy" 'string "bsub44")

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to firebolt

    You said that you're using maestro only, yet the earlier screenshot was from ADE XL.

    LSCS is the newer job submission implementation which is designed for greater scalability and has lightweight processes for the various steps rather than invoking a whole virtuoso which consumes resources (particularly memory) for long periods of time whilst simulations are running.

    Your new screenshot shows the number of jobs being 300, so if you're having an issue with it being limited, by far the best solution would be to contact customer support. That's what it's for...

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • firebolt
    firebolt over 2 years ago in reply to Andrew Beckett

    I fired sims on LSCS. Simulations are running. But when I check job setup again, it is switched back to ICRP. What I am missing here?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to firebolt

    Are you using a non-Cadence simulator? I can't think of any reason why it would switch back other than that (in current releases LSCS is not supported for third-party simulators), or maybe there's some customisation in your environment overriding job policies.

    Please contact customer support, as I said before.

    Regards,

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • firebolt
    firebolt over 2 years ago in reply to Andrew Beckett

    Thanks Andrew for your reply. I will check my settings.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information