On Mar 13, 10:28 am, [EMAIL PROTECTED] wrote:
> Thanks for the reply. To be a little more specific, we have internally
> tens of thousands of Perl modules. Before running them in production:
> we profile these modules, pass them through a circular reference
> detector (code that intercepts all allo
I've re-ordered things because gmail's love of top posting confuses the flow
of the narrative.
> On Mar 12, 5:43 pm, [EMAIL PROTECTED] (Chromatic) wrote:
> > On Monday 12 March 2007 14:29, [EMAIL PROTECTED] wrote:
> >
> > I wish I had better news for you, but I'm not sure anyone can answer your
>
>From ozgun:
>
> Inlining replies.
>
>> 1. What's the environment; Solaris, GNU/Linux, *nix, Windows?
>
> Linux.
>
>> 2. What hard information do you have on the resources being used? Have
>> you been able to profile it? Pareto's Law applies surprisingly often.
>
> Tons. In fact, we have more infor
On Mar 13, 10:28 am, [EMAIL PROTECTED] wrote:
> Thanks for the reply. To be a little more specific, we have internally
> tens of thousands of Perl modules. Before running them in production:
> we profile these modules, pass them through a circular reference
> detector (code that intercepts all allo
Thanks for the reply. To be a little more specific, we have internally
tens of thousands of Perl modules. Before running them in production:
we profile these modules, pass them through a circular reference
detector (code that intercepts all allocations, and at certain
intervals walks over Perl's S
On 12 Mar 2007 14:29:49 -0700, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi all,
I'd like to get opinions from developers on this list. I'm looking
into this system that executes massive amounts of Perl 5 code on a
Perl 5.8 interpreter. The system burns tons of CPU while running Perl
code, a
On Monday 12 March 2007 14:29, [EMAIL PROTECTED] wrote:
I wish I had better news for you, but I'm not sure anyone can answer your
questions easily without a lot more information.
> I'd like to get opinions from developers on this list. I'm looking
> into this system that executes massive amounts
Hi all,
I'd like to get opinions from developers on this list. I'm looking
into this system that executes massive amounts of Perl 5 code on a
Perl 5.8 interpreter. The system burns tons of CPU while running Perl
code, and I'm speculating on ways to improve our throughput (say, 50
billion inst per
