Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Firstly, I have been using 64-bit Perl more or less exclusively for the past few years on a variety of Linux, Windows, and Mac systems, with 50+ modules (many of them XS, don't have an exact count on that, though), and have had zero issues that would have been avoided with a 32-bit Perl.

Secondly, my own anecdotal experience shouldn't mean squat to you. :-) Fortunately, the Perl module ecosystem (and Perl itself) are blessed with some of the best unit tests in the industry (see Test::More for a start). As long as your own software also has good unit tests, you are already a long way to verifying your installation.

Thirdly, if you still have any doubt, it's worth questioning whether 64-bit Perl would actually make any substantial difference in your installation. By themselves, 64-bit programs do not inherently outperform their 32-bit counterparts. There are a couple of cases where they do:

  • (The big one): Your program needs to access more than ~3GiB of RAM, go with 64-bit
  • 64-bit architectures have additional registers that can (at the C compiler level) be used to optimize some compute-intensive routines. Benchmarking is the only sane way to tell whether this will be worthwhile.

However, there's a downside: 64-bit programs are larger (again, depends, but I've seen 10-30%), and consequently use more RAM, which can increase memory traffic, which can actually degrade performance a little. Probably not terribly significant, but again, benchmark.

For "SAN Management Servers", you are probably not using significant RAM or doing anything computationally expensive (think: decoding human genome, solving chess, etc.), so to be honest, it's probably not going to make a huge difference. So, as above, unit tests (and your own functional and integration testing) will guide you.

In reply to Re: Using 64 Bit Perl for Production Scripts. by wanna_code_perl
in thread Using 64 Bit Perl for Production Scripts. by pmu

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others drinking their drinks and smoking their pipes about the Monastery: (7)
    As of 2018-06-22 00:14 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (120 votes). Check out past polls.