in reply to Large Windows network: One 32 bit perl or 32 and 64 bit perls?

Without having too much network and administration knowledge, note that having Perl installed locally has the added advantage of reducing the network traffic. Many Perl modules are relatively small files, so loading them adds some network latency if you load them from a remote location.

Of course, by carefully setting up PERL5LIB, you can make it so that each Perl tries the local directory first before falling back onto the network share, which would get you easier upgrading at the price of confusion when you install a newer version on the network and the older, local version is used instead.

  • Comment on Re: Large Windows network: One 32 bit perl or 32 and 64 bit perls?

Replies are listed 'Best First'.
Re^2: Large Windows network: One 32 bit perl or 32 and 64 bit perls?
by Boldra (Curate) on Jan 08, 2010 at 11:25 UTC
    On some systems we have a problem where perl5lib is set to something utterly useless (an old oraperl dir), forcing us to re-set it before each call.

    The network traffic issue may well be a point, but I'm optimistic the filers can handle it. In the worst case, we can load-balance the filers or switch to local installs. Local installs would just need some extra testing to make sure we have identical images on each server.



    - Boldra