• 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 SKILL
  3. Layout XL SKILL functions extremely slow in L environme...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 15701
  • 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

Layout XL SKILL functions extremely slow in L environment

Yaosan
Yaosan over 15 years ago

Is there any way to make XL functions (those with prefix "lx") run faster in the Layout L environment, for example by loading the necessary context manually? Here's the speed difference (in CPU time) as measured by the profiler for the lxComputeViaParams function used in a script (this function is called multiple times):

Layout L: took 0.71 seconds to run

Layout XL: took 0.06 second to run

Any suggestion? Thanks!

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    Hi Yaosan,

    What I see (when running in L) is that the first time around it takes longer (in my case 0.4 seconds) but the second time it takes 0.02 seconds. It seems the first time that a via is referenced takes longer - probably as it has to build the structures for it the first time around?

    If I'm running in XL, it's fast straight away. 

    I think the most likely explanation is that XL does the Via initialisation as part of its startup, whereas L does it when the vias are used.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    And by the way, in my case it was 0.4 seconds for looking at 10 different viaDefs; once I'd looked at each once, it was much faster. 0.04 seconds for the first time to access each viaDef doesn't sound "extremely" slow to me.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Yaosan
    Yaosan over 15 years ago

    Hi Andrew,

    Thanks for the feedback. Unfortunately I am not able to reproduce the cache structure like you did. It doesn't matter how many times I call the function, the speed is always about the same i.e. slow. FYI, I'm using IC 6.1.3.

    This is what I observed (and before I get to this conclusion, I was scratching my head for half a day, wondering why is my script suddenly 10x slower). First I ran my script in L environment, it takes about 8 seconds to run. Next I switch to XL environment for the same layout, the script takes less than 0.5 second to run. Then, I switch back to L environment, and now the script takes 8 seconds to run again. Undo the script, run it again in L, still 8 seconds, it doesn't speed up at all as what I would expect from the cache structure you mention.

    btw, as long as one of the layout windows is in XL mode, the script takes less than 0.5 second to run. Once all of them are in L, the script slows down again.

    I'm not sure if this has anything to do with some of the context optimization done in XL to speed some of the stuff up, but definitely there's something different that is causing the huge difference in function execution speed.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    Hi Yaosan,

    The best thing to do is to contact Cadence Customer Support and  create a service request, with some data and representative SKILL code which shows the problem. It may well be that my testing was just way too simple compared with what you're doing (since I could only spend a few minutes on it).

    If it's consistently repeatable, and you're using a recent hotfix and it still happens, I think we need to get it into R&D to get an improvement done so that L doesn't suffer from this. I can't see why it should be consistently slower with L.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Yaosan
    Yaosan over 15 years ago

    Hi Andrew, as suggested I filed a service request and it turns out this issue is related to license checkout. The workaround provided by Bhupendra, the support I worked with, is to use lmCheckOut() and lmCheckIn() to manually checkout the license before the script is ran and check it back in once it's done.

    I think it will be helpful to have information like this included in the XL function documentation, or maybe fix such license issue in the future by caching the license for a short period of time without checking in and out each time the function is ran.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    Hi Yaosan,

    Bhupendra put me on copy in the discussion with R&D; I'm sure that the right fix will be to do some kind of caching or even permament checkout of the XL license when this function is first called - but that's not been discussed enough yet to reach agreement.

    In my case the licenses were all local, so it was pretty fast. Also, I think I then opened VLS XL, and I probably had the licenses checked out the second time (which is why it was quicker the second time).

    Regards,

    Andrew.

    • 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