in reply to Hashing Memory Usage

As an irish joke goes: "could you tell me the way to tipperary?" - "well, I wouldn't start from here".

I don't have an idea either, but I see too many changes to identify "the guilty party": OS release change, hardware change, perl release change. To make shure it isn't (or is) perl's fault I would install the same version of perl (5.8.2) on the old box, run the program and start from there.

--shmem 

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Replies are listed 'Best First'.
Re^2: Hashing Memory Usage
by awkmonk (Monk) on Jul 13, 2006 at 09:00 UTC
    The problem is that the old box is the current production machine. No-one would let me go anywhere near changing that. It's beginning to look like I either need new Perl binaries, which they just might let me load, or I re-write my routine.

    'I think the problem lies in the fact that your data doesn't fit my program'.

[reply]
      Then do it the other way round. Build a 5.6.0 perl on the new box, and test that.

      --shmem 

      _($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
[reply]
        I'd love to, but now they're telling me that they are unhappy supporting software that has been 'modified' from the original.

        A big gold star for anyone who has twigged that this is a "government project".

        I wish I could work out who to hit.

        'I think the problem lies in the fact that your data doesn't fit my program'.

[reply]
      Compile perl with a prefix, and store it in your home directory, where nobody else can touch it. It should be safe.
      -nuffin
      zz zZ Z Z #!perl
[reply]

In Section Seekers of Perl Wisdom