> *Edward*: if the data is already in small chunks you
can use mem_cached
> to manage the hash. It will handle gigs of data without
problem and
> scales very well: just add another server to the
network and that is all
> (really!). The only problem is that the ruby plugin is
kinda broken. You
> can manually add/remove data from the hash, but it wont
expire itself
> automatically when the data change. Nothing that cant
be fixed, but good
> to know...
>
> But if the problem is how to manage such a large chunk
of data in a
> single process were you have to alter all the data at
once, well... I
> dont know.
memcached looks pretty cool (as does cache_fu:
http://www.slideshare.net/err/kickin-ass-with-cachefu),
but part of the
situation that I'm dealing with now (and dealt with before,
in a
separate case), is that my data isn't in the database yet,
so there's
nothing to cache.
The reason for this is that I've got a ton of stuff in text
files that
has yet to be related to each other, and I'd like to do that
quickly,
because doing it in the db (in my case, postgres), it was
taking
forever. Maybe I've just got to tweak it to load as much
into memory as
possible.
> BTW is this list only English or bilingual? Since I
couldn't check the
> archive, I didn't know...
Hey, it's a Montreal-based list, right? Feel free to use
either language.
Edward
_______________________________________________
Rubymtl mailing list
Rubymtl lists.artengine.ca
ht
tp://lists.artengine.ca/mailman/listinfo/rubymtl
|
