Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • The blog about this bug wasn't reporting it, it was highlighting the fact that RHEL *still* hadn't fixed it, and gave some interesting background, including links to the thread on the dbic list about it.

    We happen to be affected by this bug and it's really annoying - a 10% performance loss from ithreads isn't really an issue as our servers are almost entirely I/O or DB bound, adding DBIx::Class makes for sucky performance on the dev server, but fortunately our production servers don't have the problem.

    It's t


    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • Do you really need to compile the modules on every box?

      For the project at work, we install almost all CPAN deps in an app specific directory under a local user account. Those files are version controlled together with the application source.

      Release basically consists of tarring up the source tree (including deps), and release is untarring things in the correct place and running a configuration script.

      If you have different architectures on your boxes this obviously won't work without some extra maneuvers.


    • Yeah, it's a pain once you've started doing things The Wrong Way to switch to doing things The Right Way. However, it's a once-off pain, and isn't as painful as continuing to do things The Wrong Way.
  • I always compile my own perl for dev and production, and threads is the #1 reason why. I have a new #2 reason, due to RH. Thanks, RH! :-)

    We use RH and never knew about the slowdown on Slashdot (or use Perl ... if we had been using the system perl, when we moved use Perl to this new box last week it would have been terribly, terribly slow).

  • Just a shout out to let you know we appreciate your hard work out here!
  • It's not that I don't believe you... I'm actually curious what the 10% overhead is for ithreads. Do you know of a doc of this already?