?

Log in

No account? Create an account

More Async Observations

« previous entry | next entry »
Dec. 19th, 2007 | 01:38 am

Looking through the output of the latest benchmark run of libmemcached I just noticed this:

Nonblock
Testing mdelete_generate 1.119 [ ok ]
Testing delete_generate 0.983 [ ok ]

This means that the non-blocking version of the library is a tad faster then the multi delete support.

So I ask myself, is the multi delete support of value then? Does it matter if the above is true to have multi methods?

Semantic sugar is fine, but I am really wondering if it makes an ounce of sense.

I have the multi-set functions done, but I am wondering now if I should bother with committing them.

They add 3.5 K to the size of the library, which is not much.

More important is the question of whether or not they extend the library just a little too much. Each function just increases complexity. If someone can get the same performance by just writing a loop and using the asynchronous behavior, does it make much sense?

Is it just semantic sugar?

Link | Leave a comment |

Comments {4}

Brian "Krow" Aker

(no subject)

from: krow
date: Dec. 20th, 2007 09:26 pm (UTC)
Link

The question is not multi-commands per packet, the question is whether or not-async should be required for it.

Reply | Parent | Thread