2 Replies Latest reply on Feb 1, 2010 4:25 PM by tom_donnelly

    Why does my Calibre DESIGNrev become very slow when loading?


      Q:  Today I'm loading a file of 10GB OASIS on my workstation.  It's the biggest file in our database.  The workstation has 16GB of memory.  Why was the loading extremely slow?


      A:  There are many factors that may impact the loading speed of layout file in DESIGNrev.  In this case, the memory becomes the limitation factor.  OASIS files usually have much smaller size than GDSII files.  That means it has more compression internally in the file.  So when opening OASIS files, it usually takes more memory than the GDSII file because some contents need to be uncompressed in the memory to be displayed properly. When the workstation running out of physical memory, it uses harddrive to swap.  And harddrives are usually much slower than RAM.


      A rule of thumb is that your memory should be at least 3X of the OASIS file size to load it all into memory.  However, the compression rates may vary for different files.

        • 1. Re: Why does my Calibre DESIGNrev become very slow when loading?

          Hi all,


          By the way just 2 suggestions whether you face up to such slow loading.


          1.  Use the option "-noedit" which allows a read-only opening of your layout.

               For example: calibredrv -m big_layout.gds -noedit

          2.  Use also the option "-hideLayers" which hide all the layer by default.
               Indeed your are often interested by only few layers like (poly, M1,...) and you don't need to see all of them when you start DESIGNrev.

               For Example: calibredrv -m big_layout.gds -hideLayers

          • 2. Re: Why does my Calibre DESIGNrev become very slow when loading?

            If you don't need to see all the layers in the layout then you can use a layer map, and then choose "Only load mapped layers" from the options tab of the file browser.


            Layer maps were needed in early versions of Calibre Workbench because we were ignoring datatype. In order to separate datatype you had to map a layer, datatype pair to a new layer. A layer map file is a simple ASCII file that has a layer number, a datatype number and a target layer number

            5 2 20 would map layer 5 datatype 2 to layer 20 in Workbench/Designrev.

            5 -1 20 would map all datatypes on layer 5 to layer 20.


            So for example if you only need to look at layer 5, 9, 10, 11 and you don't use datatypes, the file would look like this:


            5 -1 5

            9 -1 9

            10 -1 10

            11 -1 11


            This doesn't actually change any layer, but it allows us to check "Only load mapped layers". This will not load any unmapped layers and save on memory. If you use the -noedit or -hideLayers options, we still load all the layers and use the same amount of memory.