I think what is being discussed

Don't take this to heart, but

  1. I think what is being discussed

    Is a strange way to introduce your to-date-unstated thoughts on the possible solution to the OPs problem.

    Nobody had yet discussed it.

  2. If the forked process doesn't write the data, there is no copy made.

    Be aware, you don't have to "write" to a perl hash in order to instigate COW memory to copy pages wholesale.

    Eg. Say the hash was loaded with data from a file, string keys and numeric values; and the programs doing the lookup, looks up a string, retrieves a number and then performs math with it.

    The very act of performing a mathematical operation with the value scalar, stored as a string value, will cause Perl to convert that value from an SvPV to an SvIV And that process will cause at least 2 pages and possibly 3 pages of memory to be modified.

    The value hasn't be "written", but the scalar representation of that value has and that causes copy-on-write to allocate and copy entire pages of ram.

  3. It is indeed possible to get a 198 GB memory machine from Dell.

    200GB is not a lot of ram; multi-terabyte memory machines are available, if you have the money. Eg. 32 TB machine.

    But more to the point: Using a commodity box; memory-mapped-IO; and an PCIe NVMe SSD to hold the data; 256GB of amazing quick File-based data can be made available, to as many processes as can see the SSD, for a couple of hundred quid.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
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". I knew I was on the right track :)
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^8: Highly efficient variable-sharing among processes by BrowserUk
in thread Highly efficient variable-sharing among processes by cnd

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.