On Jan 16, 2008, at 11:42, Kieran Benton wrote:
Admittedly I’m not sure whether the async jobs will be run on the same threadpool as the ASP.NET page requests or not, can anyone answer that? This could be solved by using async I/O internally in the SET operator which would wind up using IO completion ports which are very lightweight and scalable and are definitely not part of the standard page request threadpool.
This sounds close to what I do with my client. The IO is performed on a thread that is independent of whatever is requesting the command. That makes set-type operations nearly instant in the general case (when you don't care whether the operation makes it).
It's possible to have sent a response to a request and had the client disconnect before even packetizing a mutation request to memcached.
-- Dustin Sallings
