New user questions

Cal Heldenbrand cal at
Fri Apr 13 16:02:57 UTC 2007

Oh, yes I think I misread that...  however, it's a little bit of both.
We're still playing around with a few ideas, but in a scalable reality I'm
thinking of a batch of around 5,000 variables.  It should be speedy enough
to do that iteratively for each variable, but one request would be pretty
handy too.

The particular usage for this is for an "infinite search results" page.  It
displays 50 or so results, and scrolling towards the bottom of the page does
some magic AJAX'ey stuff to expand the bottom, then chop off the top of the
page.  Running this stuff directly off our DB2 servers results in an
annoying lag time, and memcache would be perfect for this.  This requires
some preemptive loading to grab a lot of ID strings, then do some more
processing in the background to be ready for the event of loading the next
set of results.

This is also just one area that is potentially going to be modified for
memcache, there are a lot of other scenarios to think about, and we're just
in the feasibility stage at the moment.  The more flexible the API /
transactions, the easier it would be to integrate to several aspects of our

Thanks for the help!


On 4/13/07, Peter Van Dijck <petervandijck at> wrote:
> I think there must be some misunderstanding. Ask said: "If you need
> tens of thousands of values set and get per request", and Cal
> answered: "Yes ..."
> Cal, you don't need to set/fetch thousands of values on *each*
> pageview, right? That would be very, very, very weird?
> So if you don't have to get *all* those values on every request, then
> your approach doesn't seem to make any sense?
> Or perhaps I misunderstand something.
> Peter
> On 4/12/07, Cal Heldenbrand <cal at> wrote:
> >
> > >
> > > Does the web servers do all the set()'s ?    If you need tens of
> > > thousands of values set and get per request, then yes - you
> > > definitely need to aggregate them.
> >
> > Yes, all of the web servers will be independently running set / get
> > operations.  So, the "easy" way to code my example is:
> >
> >   var1=20070412185933613883000000
> >   var2=20070412185952675260000000
> >    ...
> >   var300000=20070412190015441272000000
> >
> > But the most efficient way considering the memcache protocol / storage /
> > etc:
> >
> >
> > var1=20070412185933613883000000,20070412185952675260000000,...
> >    (up to 1MB of data)

Cal Heldenbrand
   FBS Data Systems
   E-mail:  cal at
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the memcached mailing list