I can't speak for 1.2.8, but for previous releases 1MB is the largest slab size. You can essentially do three different things to get around the issue:
1) hack the slabs code a bit, and recompile it so you can have a slab class for >1MB objects. 2) decrease your object sizes slightly so it will fit in < 1MB. There should be alot of easy ways to do this, for instance break your objects into multiple pieces or compress them. 3) use one of the commercial memcached products. Also, you can view information about your slabs/items using the "stats slabs" and "stats items" commands. On May 9, 3:06 am, Emanuele Rogledi <[email protected]> wrote: > Is this a memcache limit > > On Sat, May 9, 2009 at 11:40 AM, iberkner <[email protected]> wrote: > > > Is this a memcache limit or PHP limit, just looking for clarification. > > > Thanks > > > On May 7, 3:34 pm, Brian Moon <[email protected]> wrote: > > > On 5/7/09 2:24 PM, Joseph Engo wrote: > > > > > I believe the max key size is 250 bytes and the value max is 1MB. > > > > That is correct. > > > > >> Does memcache have a "key" / "value" size limit? Is that something > > > >> that can be set? > > > > No. Not without some C hacking. > > > > Brian.
