On Mon, 2009-07-27 at 21:29 -0700, S.A. wrote: > > --- On Mon, 7/27/09, Tom Evans <tevans.uk@xxxxxxxxxxxxxx> wrote: > > > From: Tom Evans <tevans.uk@xxxxxxxxxxxxxx> > > Subject: Re: Serving partial data of in-memory common data set > > To: users@xxxxxxxxxxxxxxxx > > Date: Monday, July 27, 2009, 1:04 PM > > On Mon, 2009-07-27 at 09:01 -0700, > > S.A. wrote: > > > Hello, > > > > > > We have a requirement of serving fixed set of data > > elements (text, images, > > > audio, video, etc) to a group of users coming at about > > the same time, but > > > each user requesting different set of data elements > > from the given data set. > > > > > > Data set is fixed, but what data elements are > > presented to a user is dependent > > > on user's configuration parameters and they vary from > > user to user. Other > > > than the requesting data elements of a given set, > > there is nothing that > > > is common among users and hence their requests can be > > treated as such, ie > > > as independent requests. > > > > > > What is the best way to deal with the above scenario > > so that the each > > > httpd process does not goto to either file store or db > > for each user > > > request? > > > > > > Is there a way that we can retain this data in-memory > > and depending on > > > the requesting user, we read their configuration and > > then come to the > > > in-memory data set and build a page for the user and > > serve the user? > > > > > > Appreciate any insights or pointers. > > > > > > Thanks > > > S.A. > > > > > > > http://www.danga.com/memcached/ > > > > You dont mention what language/mechanism you want to pull > > the data out; > > memcached has client libraries for almost every language > > under the sun, > > so it should be appropriate. > > > > Cheers > > > > Tom > > Hi Tom, > > I am using LAMP and additionally a regular ext3 file store > and an ldap. Most of the data is in mysql and in file store > and it is this I would like to cache and serve via php pages. > > I will checkout memcached. Thanks for the pointer. Is there > anything native to apache itself? > > Thanks > > No, but that is almost certainly by design. Caching works best the more you can scale it. Anything inside apache would be per-process, or at best, per-machine. Using memcached allows you to scale out your cache to support many backend machines. The best way to use memcached is to avoid DB queries. You can either cache your objects, so you don't need to do DB queries to load them, or cache the resultant html you would draw from the objects, so you don't even need the objects. If you can cache entire pages, apache has mod_cache and its various sub types. Cheers Tom --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|