Hey, > 1) You can set the item size to be larger than the configured memory > allocation: > > ./memcached -m 16 -I 128m > > We should at least warn that the two values are somewhat incongruous. Maybe > add this to the recent warnings discussion for cmdline arguments?
I tossed this into that long e-mail I sent a few days back; I was working on adding warnings over memory allocation, when I found that they were impossible to write without being confusing, as the memory limit is ignored in a few ways. Once I pull the trigger on that change, it should be able to warn in more useful ways when you're obliterating the memory limit. > On a related note, should we mention that this will also increase the number > of slabs up to the size of the item size you specify? Yes. If you run memcached with -v after editing, it's obvious. I was going to mention doing that in the wiki docs, and just added it to the manpage. > 2) Could we add into the output of the help that the limit for max item size > is 128mb; you get a warning when you try to set something larger than this, > but something in the output from -h would be nice. Good idea. This made me realize that I forgot to update the manpage as well. I just pushed a commit to my 'for_143' branch which adds this + the manpage update. > 3) I've updated the relevant docs in > http://dev.mysql.com/doc/refman/5.1/en/ha-memcached.html and the included FAQ > on the configurable item size, but the FAQ on the project wiki still shows the > 1MB limits and not the recent changes in 1.4.2. I don't seem to have rights to > update the pages, or I would do it myself ;) I haven't circled back to do that yet, no :) It's not a feature we'd generally encourage using, so I wasn't too excited about documenting it. On a more serious note, if you want to be able to update the official wiki, just e-mail me privately with your google account. At any moment I'll be doing some significant damage to the wiki, so just let me know what you're working on first so we don't collide :) Thanks, -Dormando
