There is too little code here to understand how it is used, and too little description to understand what if any problems you might or might not be having.

You talk about threads but there is no threading shown. If the sub refresher() is being called as a thread procedure, then utilising closures over variables that exist in the calling thread, without also sharing those variables, makes no sense at all. Those closures will be cloned each time you start a new thread, and any changes made to them will not be reflected back into the original hashes, and so will be lost when the thread ends.

You seem to be worrying about the performance, without realising that the code you are worrying about probably doesn't work. (Almost certainly doesn't, but it is impossible to tell for sure with seeing where, how and why the code is being called.)

To get any answers that are meaningful(*), you will have to post a cut-down, working demonstration of how you envisage this code working and being used.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: Will closure increase performance thread processing subroutine? by BrowserUk
in thread Will closure increase performance thread processing subroutine? by elf_firein

Title:
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, details, 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, summary, 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.