Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re: Hunting a memory eater

by tobyink (Abbot)
on Feb 27, 2014 at 14:20 UTC ( #1076400=note: print w/replies, xml ) Need Help??

in reply to Hunting a memory eater

Not that this really answers your question, but are you using an up to date version of Net::DNS? The changelog notes some bugs pertaining to memory leaks (e.g. RT#84601, RT#81942) having been fixed recently.

use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

Replies are listed 'Best First'.
Re^2: Hunting a memory eater
by McA (Priest) on Feb 27, 2014 at 15:06 UTC

    Hi tobyink,

    that was a very valuable hint (sorry, can't do more than one ++). I really assumed that I use the newset version. Sometimes I hate myself for my (not proved) assumptions.

    So, fact is, I didn't use the newest version. The output above is based on version 0.72 of Net::DNS.

    So, for the protocol I installed the newest version 0.74 and let the whole thing run again. This looks much better now even I can't explain where the fixed costs in terms of base leaks come from. The output now is:

    1240 1234 1234 1234 1233 1234 1233 1234 1234 1233

    That means I do have a kind of usage penalty, but it seems that the consumption raises not with the count of lookups. I'll see when I lookup different domains.

    Once again: Thank you for pointing out the obvious, which I haven't done: Look at the newest version and have a look at the bug history. Be sure, I will make atonement for that as it's expected from a monk. ;-)

    Best regards

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1076400]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (5)
As of 2018-04-21 06:18 GMT
Find Nodes?
    Voting Booth?