Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: domain of willfould@gmail.com designates
 64.233.184.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=Xtp2Xk5jPemA4BJ8MLNiHO07K7s+Tr8EbWpE1IHjTHZFzSRAmzHjiaxy8TzqeFDQUMHe2L8b9ZM7rMxgP99gLxN6sUnirbBUIzUYJBdu3UCCZDXhJq2JUS7wmdrO8DyqGXjiApUFeijO6MSHJy3l7/hlwSmYeBNlVTZsfp3HhP8=
Message-ID: <4b3372230603072105l30e34a28v6861ddd209597f0c@mail.gmail.com>
Date: Tue, 7 Mar 2006 21:05:26 -0800
From: "Will Fould" <willfould@gmail.com>
To: modperl@perl.apache.org
Subject: changing global data strategy
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_10593_29927286.1141794326668"

------=_Part_10593_29927286.1141794326668
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

an old issue:
   "a dream solution would be if all child processes could *update* a large
global structure."

we have a tool that loads a huge store of data (25-50Mb+) from a
database into many perl hashes at start up: each session needs access to al=
l
these data but it would be prohibitive to use mysql or another databases fo=
r
multiple, large lookups (and builds), at each session:  there are quite a
few structures, each are very big.

if the data never changed, it would be trivial; load/build just at
start-up.

but since the data changes often, we use a semaphore strategy to determine
when childern should reload/rebuild the structures (after updates have been
made).

this is painful. there has got to be a better way of doing this - I've seen
posts on memcache and other, more exotic animals.

can someone point me in the right direction: a reference/read, or a stable
modules that exist for our situation?


thanks in advance,
william

------=_Part_10593_29927286.1141794326668
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>an&nbsp;old&nbsp;issue:</div>
<div>&nbsp;&nbsp; &quot;a dream solution would be&nbsp;if all child process=
es&nbsp;could *update*&nbsp;a large global structure.&quot;</div>
<div>&nbsp;</div>
<div>we&nbsp;have a tool that loads a huge store of data (25-50Mb+) from a =
database&nbsp;into many perl hashes at start up: each session needs access&=
nbsp;to all these&nbsp;data&nbsp;but it&nbsp;would be prohibitive to use my=
sql or another databases for multiple,&nbsp;large lookups (and builds), at =
each session:&nbsp; there are quite a few structures, each are very big.
</div>
<div>&nbsp;</div>
<div>if the data never changed,&nbsp;it would&nbsp;be&nbsp;trivial; load/bu=
ild just at start-up.&nbsp;</div>
<div>&nbsp;</div>
<div>but since&nbsp;the data changes often, we use a semaphore strategy&nbs=
p;to determine when childern should&nbsp;reload/rebuild the structures (aft=
er updates have been made).</div>
<div>&nbsp;</div>
<div>this is painful. there has got to be a better way of doing this -&nbsp=
;I've seen posts on memcache and&nbsp;other, more exotic animals.</div>
<div>&nbsp;</div>
<div>can someone point me in the right direction: a reference/read, or a&nb=
sp;stable modules that exist for our situation?</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>thanks in advance, </div>
<div>william</div>

------=_Part_10593_29927286.1141794326668--