• 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. Digital Implementation
  3. tip of the week: improve run time during initial placem...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 90
  • Views 13486
  • 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

tip of the week: improve run time during initial placement

archive
archive over 18 years ago

You can cut your run time by up to 3x (for 500k instances) by not doing scan recordering during placeDesign.  You can do the following
.
. SETUP UP YOUR SCAN IN & SCAN OUT
.
setPlaceMode -noReorderScan -modulePlan
placeDesign -with_your_own_option
scanReorder
optDesign -preCts

With the above flow, the run time is reduced at the same time congestion & timing do not get worst.

li siang



Originally posted in cdnusers.org by lisiang
  • Cancel
  • archive
    archive over 18 years ago

    Hi Li Siang,

    I tried out your suggestion, but does not see improvement. The design is bigger than 500K during placeDesign. Maybe I am using scandef. There are many scan chaisn due to the use of scan compressor. I think it is a easier flow to use scandef than to define scan-in and scan-out in Encounter especially with scan compressor the scan-ins and scan-outs are at defined at hier ports.

    Do you have any idea why disable scan reordering can make placeDesign with modulePlan run faster?

    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    i assumed you are using -inPlaceOpt with -modulePlan.

    -modulePlan wil run placement multi-time with the -inPlaceOpt to improve timing. Each re-placement will cause a scan recordering. Thus turning off the scan recordering will save some run time. If you design is not timing critical, then the re-placement might not happen and you might not see the run time saving.

    li siang


    Originally posted in cdnusers.org by lisiang
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Hi Li Siang,

    I am not using "-inPlaceOpt" with -modulePlan. I using optDesign after placeDesign. This is the reason why I don't see improvement in runtime.

    In your experience, do you prefer to use "-inplaceOpt"? Somehow it appear to me that running in two steps give better result.
    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    it is design dependent. In general -inPlaceOpt with -modulePlan works pretty well due to the replacement & re-opt. In some of the block i did, i found the following woked better (gave better timing)

    placeDesing -modulePlan
    optDesign -preCts
    placeDesign -incr
    optDesign -preCts

    li siang


    Originally posted in cdnusers.org by lisiang
    • 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