On Jan 16, 2008 8:36 PM, a. <[EMAIL PROTECTED]> wrote: > > > Moreover, there are (should be) far more Gets than Sets (in my app it's a > 20:1 ratio), but Gets cannot really benefit from the async processing (only > Sets). True, if the Get would take a significant time to execute you could > fire a get request, do some work then wait for the results, but it's not the > majority. > You are of course correct, and in my app (although I've not had your client in for long enough to determine the average miss-rate) there are wildly more gets than sets, I just have a very specific case where a particular request can have its time doubled which I can avoid if I don't wait for sets to complete :)
Or is it for others? > > Anyway just submit a patch and we'll see :) > Hmm, did you manage to try my other patches ? - Ciaran
