3 Replies Latest reply on Sep 2, 2010 8:34 AM by bobby

    Any known network shared library file issues?


      Hello all,


      I am looking to see whether or not there is know issue when sharing libraries from a network server. We have moved our libraries to a server and share them across the network but experience some sever lag at times. Does anyone have any experience with this? Also, if so, are there any recommendations on server settings, HD access speed suggestions and such?


      Issue: When searching or creating a part into a library on the network share we see long lag times. At times the lag can be as short as a few seconds to as long a full minute. We are on a 100meg network working off of a dedicated file server. Mind you, this is an issue within libraries only and not with PCB creation, editing or schematic design. I feel this is an issue with the libraries exclusively.


      I would appreciate any help and info.



        • 1. Re: Any known network shared library file issues?


          I've had some rather large libraries at a few of my employers and that initial search can certainly slow things down. Do you have a large library? Do you have a long list of libraries setup in your Library Manager? Try removing some of them. When doing a serch for a part limit yourself to one library at a time instead All Libraries. Don't just search with a wildcard "*", instead use an expected character with the wildcard like "*res* for a resistor. These are suggestions that will speed things up.



          • 2. Re: Any known network shared library file issues?

            Hi Bobby,


            There are possibly multiple issues.


            Ever since the VeriBest days (if you are talking Expedition PCB, not PADS) forward annotation has always been VERY slow over a network compared to having the library on a local drive. From network tracing I have done this appears to be at least partially due to inefficient data accessing combined with no data caching. (The operating system will cache local drive data but not network data.)


            In more recent years we have had problems with strange, random delays (up to a minute on occasions) when accessing our network-located library, whether it be from the schematic or from Expedition. It happens much more on some workstations than on others. Recently we have discovered that the delays are effected by which network switches are in the path between workstation and server. e.g. change a user from a 1G switch to a slower 100M hub can almost completely eliminate the random delays. The interesting/strange/worrying thing is that these apparently network-related problems are not evident in any other software we use - and we do company all work on network drives, nothing local.


            It can be a major frustration at times, but it is not until you compare it to a local library that you realise how bad it is. (We don't do the comparison which is why users tolerate it.)



            • 3. Re: Any known network shared library file issues?

              Thank you both for your replies. I have noticed the best improvment's come when we limit the number of libraries in the stack. We have come to use just a few client / house libraries full time and load others as needed. For the last few weeks we have been running smoothly and I will report back any additional changes.


              Thanks again,