> I just noticed that I didn't answer this question from Dormando: "Is > the only reason to keep it exactly the way it is because it's already > done and you have customers who rely on it?"
I was actually asking the couchbase folks why they were so insistent on pushing the feature the way it was, which runs all that code in the hot path every time. > Nothing is cast in stone at this stage. If there is something else > that should be included that is important for operational monitoring, > then please suggest(!) I've been procrastinating like a bastard and still don't have any method of actually verifying any of the work we've been doing. Had a couple false starts on a bench setup, then hauled off and rewrote the guts of another project I work on. Now I feel refreshed and more willing to tackle this issue again :) The problem is still, same as it was before, that we can discuss this to death but we need to actually test it to see where it's worth putting effort. In my experience of trying to break memcached, it's always been a little surprising where you end up bottlenecking performance-wise. -Dormando
