database-independence: it has begun.
ecahill at corp.untd.com
Tue Jan 2 18:12:59 UTC 2007
For me, having to add memcache in front of mogile means that each mogile
installation would have to add their own memcache. If memcache could be
turned on in the trackers, then everyone that wants it could get it for
From: mogilefs-bounces at lists.danga.com
[mailto:mogilefs-bounces at lists.danga.com] On Behalf Of Travis Boucher
Sent: Tuesday, January 02, 2007 10:58 AM
To: mogilefs at lists.danga.com
Subject: Re: database-independence: it has begun.
Hill, Greg wrote:
>> But for now I just want to remove all the 50 (er, 48 now) users of
>> get_dbh() and make them go through the store interface, then we can
>> with pretty namings.
> This will help a lot. We want to throw memcache in front of the
> and having it all centralized like that will make it trivial (or at
> least, a lot easier). I might be able to help change all the old
> database calls starting later today, I'll let you know. Is there a
> preferred method you want me to follow to verify I don't break
> I imagine that re-running all the tests after each change should cover
> it, but if there's more to it, let me know.
I don't know if you really want to add memcached at the tracker level.
By caching on the client side, not only do you take load off the
databases, you take load off of the trackers. You'd be better off
writing a layer on top of the client side API to do the caching. Its
alot easier to scale the client side of mogilefs then it is to scale the
server (tracker + database) side of things.
More information about the mogilefs