in reply to Re^2: adding a hash to a shared object
in thread adding a hash to a shared object

Wasn't this enough

Not really. The only question you ask there is: "How can I share the multilevel hash reference returned by JSON->new->utf8->decode?". Which I answered with a reference to shared_close().

But that doesn't give us the possibility of suggesting a different approach to achieving your actual goal, rather than just telling you how to implement one small part of your current approach to achieving that goal.

I'd like to see you post a standalone, single-threaded program with some sample data, that achieves the overall goal. We could then explore the potential for gains through threading, and perhaps, offer an implementation that achieves that, whilst playing to the strengths and avoiding the known weaknesses in the Perl threading model.

I'm fairly adept with threading in general and ithreads in particular, and I strongly recommend starting from a working single threaded program as a base.

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.
RIP an inspiration; A true Folk's Guy

Replies are listed 'Best First'.
Re^4: adding a hash to a shared object
by daverave (Scribe) on Aug 11, 2010 at 15:19 UTC
    You are probably right, the problem is it's quite difficult for me to strip out this piece of code out of its context, which is relatively large. Simply posting the code as-is will do no help (you could not really run it) and adapting it to a form that will be friendly for you is a tedious job (that may come out as I'm too lazy to help you help me but be sure I really appreciate all your help here!)

[reply]
      adapting it to a form that will be friendly for you is a tedious job

      You shouldn't do it for me; you should do it for you. Unless you have a provably correct and realistically profiled single-threaded version; you'll never know if your multi-threaded version produces the correct result, or what if any benefit the threading achieved.

      If it is so complex to knock up a single-threaded version of the problem, history shows that your chances of getting a multi-threaded version correct using the first approach you think of--even if you were full conversant with Perl's threading mechanisms, strengths and limitation, which I think you'll agree you are not--are slim to none.

      But, 'tis your code and your call. Good luck!

      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.
[reply]

In Section Seekers of Perl Wisdom